• 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: Timer and RunLoop question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Timer and RunLoop question


  • Subject: Re: Timer and RunLoop question
  • From: Mike Abdullah <email@hidden>
  • Date: Tue, 29 Sep 2009 23:30:32 +0100


On 29 Sep 2009, at 22:30, Wim Lewis wrote:

And what about two timers, i.e., what happens, if one of them fires while the method associated with the other one is till executing?

It won't be able to fire until control returns to the runloop in some way.

Which is why NSTime only guarantees that a timer will not fire before the date you set for it. If the thread it's scheduled on is blocked then it can potentially fire much later.


_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden


References: 
 >Timer and RunLoop question (From: Gabriel Zachmann <email@hidden>)
 >Re: Timer and RunLoop question (From: Wim Lewis <email@hidden>)

  • Prev by Date: Re: NSTableColumn value binding + keypath over a relationship
  • Next by Date: Re: Cocoa-dev Digest, Vol 6, Issue 1394
  • Previous by thread: Re: Timer and RunLoop question
  • Next by thread: NSTableColumn value binding + keypath over a relationship
  • Index(es):
    • Date
    • Thread