On 12/07/2009 11:25 AM, Vincent van Ravesteijn wrote:
rgheck schreef:
On 12/04/2009 03:26 PM, Vincent van Ravesteijn wrote:
Can someone else have a look at this? You can get the crash by (a)
failing to set the hunspell path in Preferences, and then
uncommenting the Frontend::Alert line in
HunspellChecker::Private::addSpeller().
I don't get a crash. Just a warning that my path is empty and that's
it.
Here I get this:
0 raise /lib64/libc.so.6 0 1 abort
/lib64/libc.so.6 0 2 __replacement_assert c++config.h
1728 3 std::basic_string<wchar_t, std::char_traits<wchar_t>,
std::allocator<wchar_t> >::operator[] basic_string.h 740 4
lyx::Paragraph::isWordSeparator Paragraph.cpp 2507 5
lyx::Paragraph::locateWord Paragraph.cpp 3037 6
lyx::Paragraph::spellCheck Paragraph.cpp 3099 7
lyx::TextMetrics::drawParagraph TextMetrics.cpp 2153 8
lyx::TextMetrics::draw TextMetrics.cpp 2071 9
lyx::BufferView::draw BufferView.cpp 2652 10
lyx::frontend::GuiWorkArea::updateScreen GuiWorkArea.cpp 989
11 lyx::frontend::GuiWorkArea::redraw GuiWorkArea.cpp 432
12 lyx::frontend::TabWorkArea::on_currentTabChanged
GuiWorkArea.cpp 1508 13
lyx::frontend::TabWorkArea::qt_metacall moc_GuiWorkArea.cpp
208 14 QMetaObject::activate(QObject*, int, int, void**)
/usr/lib64/libQtCore.so.4 0 15
QTabWidget::currentChanged(int) /usr/lib64/libQtGui.so.4 0
16 ?? /usr/lib64/libQtGui.so.4 0 17
QTabWidget::qt_metacall(QMetaObject::Call, int, void**)
/usr/lib64/libQtGui.so.4 0 18
lyx::frontend::TabWorkArea::qt_metacall moc_GuiWorkArea.cpp
197 19 QMetaObject::activate(QObject*, int, int, void**)
/usr/lib64/libQtCore.so.4 0 20
QTabBar::currentChanged(int) /usr/lib64/libQtGui.so.4 0 ...
<More>
and a bunch of errors to the console that look more or less like this:
QPainter::setRenderHint: Painter must be active to set rendering hints
QPainter::setRenderHint: Painter must be active to set rendering hints
QPainter::pen: Painter not active
QPainter::setPen: Painter not active
QPainter::font: Painter not active
Ah, it is only with the inline spellchecking mechanism. Now I see it too.
The inline spellchecking is done while painting the screen (?!)...
This was an optimization Abdel introduced at some point, if I remember
right. Perhaps it is dangerous and the checking should be done elsewhere.
rh
