Andre Poenitz wrote:
On Tue, Nov 07, 2006 at 12:14:46PM +0100, Abdelrazak Younes wrote:
I've tested again this document and the good news is that the performance will soon be a bit better in 1.5 with my forthcoming painting performance patch. But the problem I think Georg is right in that the problem lies in how lines and symbols are painted on screen with mathed.

While this might be true, it is also a fact that math painting has not
significantly changed since 1.2.0, in fact, this was the first component
using two-phase-drawing. So it is a bit strange that nowadays it shuld
be suddenly the bottleneck.

I didn't say that mathed is the culprit here. I am just saying that the problem is triggered by mathed which uses a lot of insets apparently. I don't really know if the problem lies in the InsetIterators or the ParIterator or something else but I am pretty sure this has nothing to do with drawing anyway.

Abdel.

PS: I removed lyx-general for the recipients.

Reply via email to