OK. I've found a pattern, but I don't know how to debug effectively.
Compiling with Snow Leopard seems to have been a red herring.
Essentially, I copy my app to the test computer by putting it in a
drop box folder in a user's Public folder. If the app is run from this
location on the machine, it functions correctly. If, however, I move
it to the desktop or to Applications, then it fails and the
+initialize method doesn't seem to get called (based on console
logging).
Any advice?
John
For context, since this thread has been idle for a while:
On Sep 22, 2009, at 10:50 PM, John Baldwin wrote:
I'm missing something in the loading of an application delegate.
In my MainMenu.xib file, the File's Owner delegate connection is set
to an AppController object. File's Owner's class is set to
NSApplication.
In the AppController class, a +(void)initialize method is defined.
The +(void)initialize method gets called and my initialization
happens as expected on my development machine. Every time, it seems.
But on a second test machine, the method doesn't get called. Ever,
it seems.
Both machines are running 10.5.8.
I can't figure out what I'm missing to get the AppController class
loaded and initialized as planned. Could anyone point me in the
right direction?
On Wednesday Sep 23 3:55 PM, at 3:55 PM, Dave Keck wrote:
Does your class have a subclass, which also has a +initialize
method, which
doesn't call [super initialize]? That might cause this sort of
behavior,
because the order in which the classes load may be indeterministic.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
