Andre Poenitz wrote:
In case somebody is interested in it I attach a profile
for the UserGuide scroll test including Qt.
We spend almost a quarter of the time in
[18] 23.6 0.21 0.47 3036718 QFontMetrics::width(QChar) const
[18]
Interesting. Maybe you ought to try to enable the font width cache to
see if it makes a difference.
However, there is also
0.00 0.32 6/6
lyx::frontend::GuiView::makeToolbar(lyx::ToolbarBackend::Toolbar const&) [35]
[37] 11.0 0.00 0.32 6
lyx::frontend::QLToolbar::QLToolbar(lyx::ToolbarBackend::Toolbar const&,
lyx::frontend::GuiView&) [37]
0.00 0.26 106/106
lyx::frontend::QLToolbar::add(lyx::FuncRequest const&, std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::alloc
ator<wchar_t> > const&) [38]
0.00 0.05 6/6 QToolBar::QToolBar(QString
const&, QWidget*) [75]
0.00 0.01 6/21 QToolBar::addSeparator() [146]
1.00 0.00 6/204 lyx::qt_(std::basic_string<char,
std::char_traits<char>, std::allocator<char> > const&) [604]
0.00 0.00 6/6 QToolBar::setMovable(bool)
[4814]
which looks a bit too fat.
Indeed. We could disable toolbar checking when moving in a document with
PageDown but I don't think this use case is very meaningful. Unless of
course if you find the scrolling too slow (I don't).
Abdel.
