routines that create
documents (blank, for opening, for printing, for non-visible processing) upon
app-open occur before applicationDidFinishLaunching:. So I overrode
applicationWillFinishLaunching: since my document subclass referenced a
user-preference, needing me to initialize the user
order, and it had the various NSDocument and NSDocumentController routines
that create documents (blank, for opening, for printing, for non-visible
processing) upon app-open occur before applicationDidFinishLaunching:. So I
overrode applicationWillFinishLaunching: since my document subclass
special condition plug into the first run loop cycle of the app, since I
haven't tried this special case. But since everything should be set up properly
at this point, it should work out.
Hope this helps.
Am 30.09.2011 um 01:48 schrieb koko:
I have implemented applicationWillFinishLaunching in my
I have implemented applicationWillFinishLaunching in my app delegate but
strangely (to me) it is not called but applicationDidFinishLaunching is called
so I know my delegate is properly connected.
Are there some conditions that must be met for applicationWillFinishLaunching
to be called
to determine what those would have
been. It's a royal pain.
--Graham
On 30/09/2011, at 9:48 AM, koko wrote:
I have implemented applicationWillFinishLaunching in my app delegate but
strangely (to me) it is not called but applicationDidFinishLaunching is
called so I know my delegate
