• 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: app delegate +initialize
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: app delegate +initialize


  • Subject: Re: app delegate +initialize
  • From: Dave Keck <email@hidden>
  • Date: Tue, 22 Sep 2009 20:21:31 -1000

That certainly sounds fishy, but there's not much for us to go on. I'd
say the standard debug tactics apply: whittle down your project as
small as possible with the bug still in-tact. More often than not this
will illuminate the problem, and if not, at least you'll have some
sample code to show us.

... but if your object is instantiated by your XIB, then its class's
+initialize should certainly be called before. It's a long shot, but
perhaps you have multiple +initialize methods defined for
AppController, in several categories? If that's the case, it's
undefined which category's +initialize gets called, which could vary
between your test machines.
_______________________________________________

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: app delegate +initialize
      • From: Jens Alfke <email@hidden>
References: 
 >app delegate +initialize (From: John Baldwin <email@hidden>)

  • Prev by Date: Re: app delegate +initialize
  • Next by Date: building and running on Snow Leopard
  • Previous by thread: Re: app delegate +initialize
  • Next by thread: Re: app delegate +initialize
  • Index(es):
    • Date
    • Thread