• 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
init problems in NSTimer callback
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

init problems in NSTimer callback


  • Subject: init problems in NSTimer callback
  • From: Albert Andersen <email@hidden>
  • Date: Tue, 14 Nov 2006 12:20:02 -0800

I have a custom class that I am instantiating, and then deallocating, inside the callback of an NSTimer. The first time I do this, everything is just fine.

The second time, however, the call to init doesn't happen. When I try to step into it in the debugger, it just steps over, even if there's a break point set in the init method. Furthermore, attempts to init one of these objects outside the NSTimer callback also fail in the same way. It's almost like the init method is eliminated, though I don't even know if that's possible.

I've found a workaround by manually creating the data normally created by init and calling a new [myObject initWithData] method instead of [myObject init], but I was wondering if anyone else has run into a problem like this, and if they know what causes it.

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

  • Prev by Date: Re: controlTextDidChange vs NSNumberFormatter
  • Next by Date: init problems in NSTimer callback
  • Previous by thread: Re: Core Data/Bindings Issue re: pop-ups and multiple
  • Next by thread: init problems in NSTimer callback
  • Index(es):
    • Date
    • Thread