On Tue, Mar 10, 2009 at 11:02 PM, Kyle Sluder <kyle.slu...@gmail.com> wrote: > On Wed, Mar 11, 2009 at 1:53 AM, Roland King <r...@rols.org> wrote: >> So you just add the timer to the runloop, run it, it sleeps until the timer >> fires, does its thing and then goes back to sleep again. What am I missing? > > Well, there is a sentence directly below that list that says the following: > > "Because timers and other periodic events are delivered when you run > the run loop, circumventing that loop disrupts the delivery of those > events." > > That sentence implies that the run loop must be run, either manually > or as the result of input coming in on an input source (which timers > are not), in order for the timer to fire.
"run" basically means the thread is INSIDE a call to one of the "run" methods of a runloop (-[NSRunLoop runUntilDate:], etc.) not that the runloop is actively doing something (aka burning CPU). The runloop cannot pickup timer fires, event source fires, etc. if the thread of execution is outside of the runloop itself... that is all that statement is saying. -Shawn _______________________________________________ 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
