The NSApplicationDidFinishLaunchingNotification is posted (at
least at my ppc) right
after the delegate returns.
That sounds strange: the notification is the argument of
applicationDidFinishLaunching:, so it's usually posted by
finishLaunching just before, not after, and the call to the delegate
is the standard response. Are you sure you let your delegate be called
properly?
I've got a NSLog() in the delegate method and in the method that is
called by the notification (that i registered just for debugging
purposes). So I can see that the notification is surely called after the
delegate method. The delegate is set in the Interface Builder as the
delegate of File's Owner.
I did not register any Observer for this Notification.
You don't need to, assigning a delegate to the application is enough.
Are you overriding finishLaunching too? According to the docs:
"If you override finishLaunching, the subclass method should invoke
the superclass method."
If you mess with the process, stranger things can happen...
I did not subclass NSApplication.
And why does this fail on the intel machine and not on the ppc
machine.
Without any code, that's difficult to say: as a vague (and probably
completely wrong in this case) suggestion, look after endian issues.
I know that, but I'am pretty sure you do not like to review all the code
of my application. And I just don't know which code to paste because as
far as I see the bad access does not happen in my code. Am I right with
this point? Is it right that it happens within the posting of the
notification and outside of my delegate?
Stefan
_______________________________________________
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
