Re: NSTimer firedate randomly changes
Re: NSTimer firedate randomly changes
- Subject: Re: NSTimer firedate randomly changes
- From: Kyle Sluder <email@hidden>
- Date: Wed, 17 Nov 2010 13:54:47 -0800
On Wed, Nov 17, 2010 at 1:54 PM, Greg Parker <email@hidden> wrote:
> On Nov 17, 2010, at 1:35 PM, Kyle Sluder wrote:
> > That's not how timers work. They only fire if something wakes the runloop
> > after their time has expired. Usually this is an event.
>
> Not true. A timer may fire some time after its fire date for any number of
> reasons, but "no event to wake the run loop" is not one of them. If the run
> loop is idle (and in the right run loop mode, and not stopped, etc), then a
> timer's expiration is itself sufficient to wake the run loop and call the
> timer's code. No other event is necessary.
>
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
--Kyle Sluder
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden