Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Don't you think that this is a waste of CPU cycles? The
Abdelrazak> update machinery is done anyway because this
Abdelrazak> LyXText::setLayout() method is called only twice in two
Abdelrazak> LFUNs in text3.C: LFUN_FLOAT_LIST and LFUN_LAYOUT.
Considering the amount of CPU cycles that may be wasted here
(negligible), we should choose the solution which leads to the safest
and easier to understand code, and not worry about performance.
Well, I don't think it is any easier to understand. Have you tried to
run LyX step by step through a debugger? The lfun machinery is awfully
complicated. And I am not so sure the performance penalty is negligible.
But OK, point taken. I understand your reticence and I will explore
another solution. Maybe it's the time to cleanup the lyxfunc/LyXView
interaction. But I expect another lengthy discussion and I am not sure I
am prepared for another round.
Abdel.
