• 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: NSTimer and a problem with document-based apps
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSTimer and a problem with document-based apps


  • Subject: Re: NSTimer and a problem with document-based apps
  • From: Todd Heberlein <email@hidden>
  • Date: Sat, 26 Jul 2008 16:30:24 -0700

- (id)init {
...
timer = [NSTimer scheduledTimerWithTimeInterval:10.0
...
}
...

That new instance of course calls init, and suddenly I have two NSTimers
running when I only wanted one timer for the whole app.

I think you want to make your timer a global variable and then initialize it within a call to a +load or +initialize method for one of your classes. See the following link:


http://developer.apple.com/documentation/DeveloperTools/gcc-3.3/gcc/Executing-code-before-main.html

Todd

_______________________________________________

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


  • Follow-Ups:
    • Re: NSTimer and a problem with document-based apps
      • From: "Sumner Trammell" <email@hidden>
References: 
 >NSTimer and a problem with document-based apps (From: "Sumner Trammell" <email@hidden>)

  • Prev by Date: Re: NSTimer and a problem with document-based apps
  • Next by Date: CGDisplayBounds vs NSSCreen visibleFrame
  • Previous by thread: Re: NSTimer and a problem with document-based apps
  • Next by thread: Re: NSTimer and a problem with document-based apps
  • Index(es):
    • Date
    • Thread