On 08/11/2009 10:37 AM, Vincent van Ravesteijn - TNW wrote:
btw in gnome or kde you are going to be asked in the same way as in
windows nowadays or is that direct kill signal from dekstop manager?
I think we get a signal from Qt. See e.g. GuiView::closeEvent().
That's the crux, what do you mean by 'a' signal.
QMainWindow::closeEvent(QCloseEvent * close_event) or
QApplication::event(Qevent * ev) ?
0 lyx::frontend::GuiView::closeBufferAll GuiView.cpp 583
1 lyx::frontend::GuiView::closeEvent GuiView.cpp 544
2 QWidget::event(QEvent*) /usr/lib64/libQtGui.so.4 0
3 QMainWindow::event(QEvent*) /usr/lib64/libQtGui.so.4 0
4 lyx::frontend::GuiView::event GuiView.cpp 890
5 QApplicationPrivate::notify_helper(QObject*, QEvent*)
/usr/lib64/libQtGui.so.4 0
6 QApplication::notify(QObject*, QEvent*) /usr/lib64/libQtGui.so.4 0
7 lyx::frontend::GuiApplication::notify GuiApplication.cpp 1303
8 QCoreApplication::notifyInternal(QObject*, QEvent*)
/usr/lib64/libQtCore.so.4 0
9 QWidgetPrivate::close_helper(QWidgetPrivate::CloseMode)
/usr/lib64/libQtGui.so.4 0
10 QApplication::x11ClientMessage(QWidget*, _XEvent*, bool)
/usr/lib64/libQtGui.so.4 0
11 QApplication::x11ProcessEvent(_XEvent*) /usr/lib64/libQtGui.so.4 0
12 ?? /usr/lib64/libQtGui.so.4 0
13 g_main_context_dispatch /lib64/libglib-2.0.so.0 0
14 ?? /lib64/libglib-2.0.so.0 0
15 g_main_context_iteration /lib64/libglib-2.0.so.0 0
16
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
/usr/lib64/libQtCore.so.4 0
17 ?? /usr/lib64/libQtGui.so.4 0
18 QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
/usr/lib64/libQtCore.so.4 0
19 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)
/usr/lib64/libQtCore.so.4 0
20 QCoreApplication::exec() /usr/lib64/libQtCore.so.4 0
... <More>
So I think it's the former.
rh
rh
Vincent
