Am Sonntag, den 06.12.2009, 18:53 -0500 schrieb Ben M.: > On Sun, Dec 6, 2009 at 4:43 PM, Peter Kümmel <syntheti...@gmx.net> wrote: > > Before the patch LyX was single-threaded; means, processing an > > user-event, like pressing a button, had to wait until all previewing > > is done. > > I never had to wait for "Instant Preview." Is that not classified as > a "user-event"? > > >> I have no idea what I'm looking for. The buffer is > >> still frozen while rendering a preview. Do you expect this??? > > > > No, I wonder why. Is it really frozen, or is the cursor only invisible. > > Could you scroll the view? > > Occasionally I can move the cursor around, but the vast majority of > the time, the buffer freezes. I cannot use the scrollbars. (I > suspect that for the few times when I could move the cursor, I had not > modified the buffer, so LyX was not actually rendering anything new.)
Seems LyX is busy within it's own thread, then processing events while a process is running doesn't help much. The initial idea of the patch was to show only progress information, so you can see what LyX is doing and is not blocked only. > > > But there are still a moments when LyX is frozen. Only when external > > tools like latex or bibtex are busy the GUI could react on user input. > > When LyX generates internally the TeX code it is still blocked, because > > this is not done in a separate thread. > > Internal generation of TeX code is very quick for me. What slows > things down the most is when LaTeX reruns several times to generate my > references. > > Please excuse my ignorance, but why can't we simply perform exports > the same way that we currently generate instant previews? No problem, disabling the changes is simple. How does instant preview work? What means 'instant' in this context? Does it use threads Peter
