Vincent van Ravesteijn - TNW wrote: > That's the crux, what do you mean by 'a' signal. > QMainWindow::closeEvent(QCloseEvent * close_event) or > QApplication::event(Qevent * ev) ?
I don't know if it's relevant, but LyX.cpp has this comment: /* Signals and Windows =================== The SIGHUP signal does not exist on Windows and does not need to be handled. Windows handles SIGFPE and SIGSEGV signals as expected. Ctrl+C interrupts (mapped to SIGINT by Windows' POSIX compatability layer) cause a new thread to be spawned. This may well result in unexpected behaviour by the single-threaded LyX. SIGTERM signals will come only from another process actually sending that signal using 'raise' in Windows' POSIX compatability layer. It will not come from the general "terminate process" methods that everyone actually uses (and which can't be trapped). Killing an app 'politely' on Windows involves first sending a WM_CLOSE message, something that is caught already by the Qt frontend. For more information see: http://aspn.activestate.com/ASPN/Mail/Message/ActiveTcl/2034055 ...signals are mostly useless on Windows for a variety of reasons that are Windows specific... 'UNIX Application Migration Guide, Chapter 9' http://msdn.microsoft.com/library/en-us/dnucmg/html/UCMGch09.asp 'How To Terminate an Application "Cleanly" in Win32' http://support.microsoft.com/default.aspx?scid=kb;en-us;178893 */ Jürgen
