Re: Crash when using [NSTimer fire]
Re: Crash when using [NSTimer fire]
- Subject: Re: Crash when using [NSTimer fire]
- From: Shawn Erickson <email@hidden>
- Date: Fri, 19 Nov 2004 10:13:03 -0800
On Nov 19, 2004, at 9:55 AM, Gwynne wrote:
On Nov 19, 2004, at 12:39 PM, Shawn Erickson wrote:
Why are using using a timer that way? I don't follow how a timer of 5
years is useful...
Guessing at what you are attempting to do... consider using an
NSConditionLock or some such thing if you are trying to gate
something from running, etc.
It's not always used that way. The timer has a variable interval. The
5-year interval is used when the associated UI object has been
disabled so that I don't have to keep checking whether or not the
timer exists. It's a convenience.
Consider using NSDate distantFuture for you date.
<http://developer.apple.com/documentation/Cocoa/Reference/Foundation/
ObjC_classic/Classes/NSDate.html#//apple_ref/doc/uid/20000188/
distantFuture>
I have never seen or heard of an issue with long period timers. You may
want to post a code sample that can reproduce the failure and file a
bug with it.
-Shawn
_______________________________________________
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