• 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: perform ... afterDelay?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: perform ... afterDelay?


  • Subject: Re: perform ... afterDelay?
  • From: goessly <email@hidden>
  • Date: Wed, 4 Jan 2006 21:28:52 +0100

You don't really want to wait 0.04 seconds, you want to have a method called 25 times per second.
Basically yes, but I would have expected the scheduler to assign the resulting downtimes to other tasks? If this is not the case, an NSTimer would indeed be better...
But since the loop in question breaks after one second and isn't called to many times... maybe there's no harm in "giving it time"? Or would this be to inefficient?


goessly
_______________________________________________
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


  • Follow-Ups:
    • Re: perform ... afterDelay?
      • From: John Stiles <email@hidden>
References: 
 >perform ... afterDelay? (From: goessly <email@hidden>)
 >Re: perform ... afterDelay? (From: Jeff LaMarche <email@hidden>)
 >Re: perform ... afterDelay? (From: Marco Scheurer <email@hidden>)
 >Re: perform ... afterDelay? (From: goessly <email@hidden>)
 >Re: perform ... afterDelay? (From: Marco Scheurer <email@hidden>)

  • Prev by Date: Re: MainMenu
  • Next by Date: Re: MainMenu
  • Previous by thread: Re: perform ... afterDelay?
  • Next by thread: Re: perform ... afterDelay?
  • Index(es):
    • Date
    • Thread