On Thu, Mar 13, 2008 at 9:37 PM, Brian Greenstone <[EMAIL PROTECTED]> wrote: > I'm hoping someone can shed some light on this for me. I'm getting > some unusual retainCount values from the following code: > > NSTimer *theTimer; > > theTimer = [NSTimer scheduledTimerWithTimeInterval:1.0 > target: self > selector: > @selector(timerCallback) > userInfo: nil > repeats: YES]; > > NSLog(@"A: retain count: %i", [theTimer retainCount]); > > [[NSRunLoop currentRunLoop] addTimer: theTimer forMode: > NSDefaultRunLoopMode]; > > NSLog(@"B: retain count: %i", [theTimer retainCount]); > > > The output I get is: > > A: retain count: 2 > B: retain count: 2 > > > But that shouldn't be, right? Shouldn't the retainCount of theTimer > be 1 after scheduledTimerWithTimeInterval? Then shouldn't it be > bumped up to 2 after adding the timer to the Run Loop?
The timer creation *already* adds it to the runloop (this is why it has "scheduled" in the name), which gives you a retain count of 2 and causes the manual scheduling to do nothing at all. Mike _______________________________________________ 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 [EMAIL PROTECTED]
