Jean-Marc Lasgouttes wrote:
Helge Hafting <[EMAIL PROTECTED]> writes:
I agree. The speed is ok on most modern machines. Still, if we
can avoid doing "way too much" all the time, then LyX will
not only be ok, but also outrun those other "ok" apps out there.
Not necessarily. Only profiling tells you what is really using up all
the time.
Just as an experiment, I ran a gprof-enabled LyX and just kept my
finger on letter 'f'. Toolbars::update uses 13.5% of the time:
[15] 13.5 0.00 0.32 1157 lyx::frontend::Toolbars::update(boo
l, bool, bool) [15]
0.00 0.32 1157/1157 lyx::frontend::Toolbars::update
() [16]
0.00 0.00 9256/9256 lyx::frontend::Toolbars::displa
yToolbar(lyx::ToolbarInfo const&, bool) [555]
That may seem to be a lot, but remember that all work done by Qt and X
(drawing, metrics...) is ignored here. So this 13.5% is vastly
overestimating the situation.
I am not 100% sure but I don't think so. Unless you are talking about
the drawing of the toolbars themselves, all drawing/metrics operations
have already been done at this stage so the 13.5 really are taken by
Toolbars::update(). And even if you are talking about toolbars
redrawing, this is happening at the same time as the rest of the LyXView
when the main window receive a paint event. So that is after
Toolbars::update().
Abdel.
