• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Nightmare with NSTimer
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Nightmare with NSTimer


  • Subject: Re: Nightmare with NSTimer
  • From: Mike Shields <email@hidden>
  • Date: Thu, 13 Feb 2003 02:22:34 -0700

Colin,

-isValid: returns whether or not the timer is currently scheduled on a runloop and will fire. It has nothing to do with it being a real object or not. If you create a timer with the convenience methods +scheduledTimerWithTimeInterval:..., it will be scheduled on the current runloop. If you don't retain this object that they return, there's nothing keeping it around past when the timer fires. Just remember the rules of retain/release and you'll be fine. Since you want to hold onto it past when the timer fires, you have to retain it yourself.

Mike
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >Nightmare with NSTimer (From: Colin Jackson <email@hidden>)

  • Prev by Date: Nightmare with NSTimer
  • Next by Date: Limiting NSString length without knowing the length
  • Previous by thread: Nightmare with NSTimer
  • Next by thread: Limiting NSString length without knowing the length
  • Index(es):
    • Date
    • Thread