From 90630409cbe8740d2c8b66823757a4ea5441aa21 Mon Sep 17 00:00:00 2001 From: Manolo Gouy Date: Tue, 6 Feb 2018 17:56:47 +0000 Subject: Beef up documentation of how FLTK handles cmd-Q/Quit xxx events under MacOS. git-svn-id: file:///fltk/svn/fltk/branches/branch-1.4@12648 ea41ed52-d2ee-0310-a9c1-e6b18d33e121 --- documentation/src/osissues.dox | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) (limited to 'documentation/src/osissues.dox') diff --git a/documentation/src/osissues.dox b/documentation/src/osissues.dox index 166c0a95d..82472c274 100644 --- a/documentation/src/osissues.dox +++ b/documentation/src/osissues.dox @@ -738,9 +738,17 @@ Apple "Quit" Event \par When the user presses Cmd-Q or requests a termination of the -application, OS X will send a "Quit" Apple Event. FLTK handles -this event by sending an \c FL_CLOSE event to all open -windows. If all windows close, the application will terminate. +application, FLTK reacts sending an \c FL_CLOSE event to all open +windows. If any window remains open, the termination request aborts. +If all windows close, the application's event loop terminates, +that is, Fl::run() returns. The application can then follow +FLTK's normal termination path executing cleanup code that may be programmed +after termination of the event loop, and returning from main(). +Function Fl::run_also_windowless() can be used instead of Fl::run() to keep +the event loop running also after all windows are closed, a feature the MacOS platform supports. +This function also returns after a successful Cmd-Q. +Function Fl::program_should_quit() allows to detect whether the event loop +terminated because of a program termination request. Apple "Open" Event -- cgit v1.2.3