Re: NSTimer fires after invalidated - why?
Re: NSTimer fires after invalidated - why?
- Subject: Re: NSTimer fires after invalidated - why?
- From: Cameron Hayne <email@hidden>
- Date: Thu, 23 Mar 2006 12:20:48 -0500
On 23-Mar-06, at 12:09 PM, John Stiles wrote:
If the computer hiccups for more than "delay" seconds for any
reason, could this technique result in your selector being called
early?
Yes, I think that could be a problem. But the same problem would
arise with any time-based method (e.g. NSTimer). I don't really
consider it a problem, though, since if the computer hiccups, then
the user is not doing whatever they were doing that caused me to want
to delay the selector. I.e. so far, I have always used this in order
to get something to happen after the user has paused in some action
(e.g. resizing a window).
--
Cameron Hayne
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden