On 09/08/2010 09:19 AM, Pavel Sanda wrote:
Richard Heck wrote:
I don't really understand this either, but it certainly look as if the
updateMacros() calls are eating a lot of time. Just on general grounds, we
need to call it only when we must. There is surely no need to call
updateMacros just when you are moving the cursor.
I just had a quick look at this. I think we should try commenting out the
line:
buffer_.updateMacros();
at line 418, BufferView::processUpdateFlags(). You'll see that I put a
i'll try to do this locally.
The question is whether it breaks something else.
i guess that math macros break somewhere..
If so, I think we could restore the call when needed. The question would
be when it breaks. But, as I say in the FIXME, it's hard to see how the
macros need updating if the buffer doesn't.
rh
