Here's what I got from that documentation: - An NSTimer is a run loop source.
- NSRunLoop monitors its sources for events, provided that the run loop is running in the mode that the source is scheduled in. - If the run loop is processing an event from a different source and a timer fires, then the run loop will process the timer event on a subsequent iteration. - If the run loop is not running at all (like, you created an NSThread and didn't -run the run loop, or you are creating a foundation tool and didn't -run the run loop), then the timer events will not be processed, because the run loop is not processing *any* events. - If the run loop is not operating in the mode that the timer is scheduled in, then the timer events will not be processed until the run loop begins running in that mode again. Seemed like pretty straight-forward documentation to me. Dave On Nov 17, 2010, at 2:54 PM, Kyle Sluder wrote: > Okay, that's two people who have corrected me on this now. What am I > misinterpreting about this documentation: > > http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/Multithreading/RunLoopManagement/RunLoopManagement.html _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
