Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added lengthy comment detailing the implications of idle handling

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@24137 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
David Elliott
2003-10-09 15:59:37 +00:00
parent 9670dfc4be
commit 59d6b6a928
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
src/cocoa/app.mm
View File

@@ -239,6 +239,16 @@ void wxApp::CocoaInstallIdleHandler()
// Call doIdle for EVERYTHING dammit // Call doIdle for EVERYTHING dammit
// We'd need Foundation/NSConnection.h for this next constant, do we need it? // We'd need Foundation/NSConnection.h for this next constant, do we need it?
[[ NSRunLoop currentRunLoop ] performSelector:@selector(doIdle:) target:m_cocoaAppDelegate argument:NULL order:0 modes:[NSArray arrayWithObjects:NSDefaultRunLoopMode, /* NSConnectionReplyRunLoopMode,*/ NSModalPanelRunLoopMode, /**/NSEventTrackingRunLoopMode,/**/ nil] ]; [[ NSRunLoop currentRunLoop ] performSelector:@selector(doIdle:) target:m_cocoaAppDelegate argument:NULL order:0 modes:[NSArray arrayWithObjects:NSDefaultRunLoopMode, /* NSConnectionReplyRunLoopMode,*/ NSModalPanelRunLoopMode, /**/NSEventTrackingRunLoopMode,/**/ nil] ];
/* Notes:
In the Mac OS X implementation of Cocoa, the above method schedules
doIdle: to be called from *within* [NSApplication
-nextEventMatchingMask:untilDate:inMode:dequeue:]. That is, no
NSEvent object is generated and control does not return from that
method. In fact, control will only return from that method for the
usual reasons (e.g. a real event is received or the untilDate is reached).
This has implications when trying to stop the event loop and return to
its caller. See wxEventLoop::Exit
*/
} }
void wxApp::CocoaDelegate_applicationWillBecomeActive() void wxApp::CocoaDelegate_applicationWillBecomeActive()