[EMAIL PROTECTED] wrote: > I would be happy to help with finding the bug, thats why I send a copy > of this to the devel-list. > > Splitting the document into parts would only be a crutch, since I often > need to manage references > to earlier theorems, to equation numbers, etc..
That works well as long as you open the child documents from the master document. Then references etc are known across all parts. > I could imagine a feature like "folding away" a section, so the heading > would be shown but the > section is only opened when you double-click on the section heading. That would be nice to have anyway. > Another possibility, I could imagine, is making the generated pngs > resident, so they need not be > generated again when I start lyx with the same document next time. One > problem, however, is > that I am working on the same document at work during the day, and at > home in the evening. I don't think that the previews are the problem. Surely it takes some time ot process them, but this is done iun the background, and although LyX is a bit slower until they are generated it is still usable (at least on linux). > (By the way, the reported behaviour is the same on both computers. It > could not only be faulted > to csrssexe, since during the 3.5 min. of "LyX not responding" the > process manager only credits > 25% to csrss.exe and 75% to lyx.exe ) No, csrss.exe does not seem to be the problem, it only seems to be a symptom. See http://bugzilla.lyx.org/show_bug.cgi?id=2900 for more information. There was also a thread some time ago with a good explanation: http://www.mail-archive.com/lyx-users%40lists.lyx.org/msg51385.html What we know so far is that the slowness is related to math. It is improved by Instant Preview sometimes, but not completely solved. The reason is probably that the way how math insets are drawn on screen (and/or the metrics are calculated) is done in a way that is very expensive on windows. > I am indeed considering reinstalling some old version of LyX, although > this is like withdrawing my > chips from LyX ... That would be a pity, but I guess we can find the bug with the help of somebody who is able to do some profiling on windows. Unfortunately we did not really get started on that, since profilers on windows either seem to be expensive (glowcode), or complicated to use (kernrate). Georg
