Re: NSTimer question...
Re: NSTimer question...
- Subject: Re: NSTimer question...
- From: Ali Ozer <email@hidden>
- Date: Wed, 13 Apr 2005 12:48:14 -0700
Are you running this in a modal panel, or in the context of some
other processing? scheduleTimer... method adds the timer to the
default runloop mode, which doesn't fire in modal panels, event
processing, or other custom modes. You can use NSRunLoop's
addTimer:forMode: to specify other modes. Note the special mode,
(NSString *)kCFRunLoopCommonModes, which represents the default,
modal, and event processing modes, as well as any modes registered as
"common."
Ali
Begin forwarded message:
From: John Draper <email@hidden>
Date: April 12, 2005 19:57:26 PDT
To: email@hidden
Subject: NSTimer question...
I have a method like this... in my main Controller...
- (void)noAnswerIn:(NSTimeInterval)seconds
{
// Create a new timer with the new refreshtime.
if (noAnswerTimeout == nil) {
NSLog(@"Starting no-answer timer");
noAnswerTimeout = [NSTimer
scheduledTimerWithTimeInterval:seconds
target:self
selector:@selector
(noAnswer:)
userInfo: nil
repeats:NO];
}
}
- (void)noAnswer:(id)sender
{
NSLog(@"I never get here");
// I do my stuff here if after a period of "seconds" above
expires.
// of course we have to do this to ditch our timer when done.
[noAnswerTimeout invalidate]; // Ditch the timer - no longer
needed.
noAnswerTimeout = nil; // Loose reference to it.
}
I never get to the noAnswer callback. What am I missing?
What things can I do to check into why this isn't working?
John
_______________________________________________
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