> For this, the simple recursive bisection would work. I was thinking that too. But we still have the problem of choosing between dvipng (quicker) or legacy (needed by PSTricks and TikZ) mode.
> As a bonus feature, something similar to 'visual instant warnings' > from some compilers (as in '(pre)compile-time warnings') would be > possible to obtain, just by strategically using preview > insets. It would > prove useful, while creating some tricky ERTs. In fact, this usage > scenario is the main reason for me to actually write this post. Yes, it would be nice, but this would add a problematic layer, as we know from the other thread: preview-latex. > 1. There should be an option to use instant preview for > "math only", > for the cases where the user knows about the failing preview > insets, but > don't have time to fix these, If a piece of code doesn't work why put it a preview inset? Simply remove the preview inset, it's not the default for ERT insets to have instant-preview. > 2. Math previews should always be created separately, as these > rarely trigger instant preview-related problems (well, I'm > not an expert > in this area, so it is just an assumption of mine, please > correct me if > I'm wrong). Yes, it's what I proposed in my last mail. Maybe the best solution would be to generate all the math insets together (with dvipng and maybe bisection to find failing instant-previews) and all the others separately so we can still choose for each one which mode to use (dvipng or legacy). Enrico? Pavel? Julien? Pavel: why the user inteface become unresponsive while opening a document and creating all the IPs? Shouldn't this be an async operation? venom00
