Re: app delegate +initialize
Re: app delegate +initialize
- Subject: Re: app delegate +initialize
- From: John Baldwin <email@hidden>
- Date: Mon, 28 Sep 2009 21:51:00 -0700
Thanks to everyone for responding. For what it's worth, I am using the
+initialize to register defaults.
I went and upgraded to Snow Leopard and XCode 3.2, and now when I
deploy to my test machine, it works fine, and the +initialize method
gets called.
This is all very baffling. Don't know why it didn't work before. Don't
know what made it start working. I am worried that this broken
behavior will magically reappear.
Thanks again,
John
On Wednesday Sep 23 10:31 AM, at 10:31 AM, Jens Alfke wrote:
On Sep 23, 2009, at 9:44 AM, Matt Neuburg wrote:
Whoa, whoa. Let's be fair. There is some common initialization
(such as
registering defaults, esp. when bindings are also involved) that
*must* be
done in +initialize, as awakeFromNib is not early enough.
Sorry, you're right. In that sentence I was referring to object
initialization vs. -awakeFromNib.
—Jens
_______________________________________________
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