Andre Poenitz wrote:
On Thu, Jul 13, 2006 at 03:56:02PM +0200, Abdelrazak Younes wrote:
Georg Baum wrote:
Abdelrazak Younes wrote:
As a side note, I really think the coordcache concept is flawed.
Well, I guess should be a bit more diplomatic in my words. I meant that
the way the coordCache is used is flawed. What is problematic is it's
use all other the place in LyXCode without any confidence in its state.
I also think that it is (maybe) overused in some places.
No need to be diplomatic. The concept _is_ flawed because the coord
cache is not just a cache to speed up things, it also needs to be warm
at various times (most notably anytime up/down movement is required)
Yes and that was the principle source of problem. The solution I found
is to delay the second cache update to the maximum. That is just before
the final drawing.
There is a fairly simple solution to this problem: Always rebreak
paragraphs on-the-fly. However, this turned out to be too expensive.
The solution we have is good enough for now. But I'd really like to have
this cache handled by something more high level instead of having this
global variable used everywhere.
IIRC it was introduced as part of the two-step drawing scheme that
helped to get rid of lots of hacks that were present in 1.3. If it
is not properly documented somewhere please get Andre to write a
short summary.
It is actually not that hard to understand when you read the code
Certainly compared to 'lockInsetInInset' & Co.
[You have been lucky not to live in the Dark Ages, Abdel ;-}]
:-)
Abdel.
