• 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 fires after invalidated - why?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSTimer fires after invalidated - why?


  • Subject: Re: NSTimer fires after invalidated - why?
  • From: Andreas Mayer <email@hidden>
  • Date: Thu, 23 Mar 2006 08:22:52 +0100


Am 23.03.2006 um 07:38 Uhr schrieb Walt Horat:

I do appreciate the efficiency of implementing this, as with most things
cocoa, it is trivial to make the framework do what I want.

Just for the record - there's a way to even avoid explicitly allocating a timer:


[NSObject cancelPreviousPerformRequestsWithTarget:m_drawer selector:@selector(close:) object:self];

[m_drawer performSelector:@selector(close:) withObject:self afterDelay:5.0];


Andreas _______________________________________________ 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: NSTimer fires after invalidated - why?
      • From: Cameron Hayne <email@hidden>
References: 
 >Re: NSTimer fires after invalidated - why? (From: Walt Horat <email@hidden>)

  • Prev by Date: Re: value transformer for structs?
  • Next by Date: Re: Source files - subclassing a nstableview
  • Previous by thread: Re: NSTimer fires after invalidated - why?
  • Next by thread: Re: NSTimer fires after invalidated - why?
  • Index(es):
    • Date
    • Thread