On Sep 15, 2010, at 7:30 PM, Kyle Sluder wrote:
> On Wed, Sep 15, 2010 at 7:11 PM, Jerry Krinock wrote:
>> Anything that I want to happen before a document opens, in case the app is
>> launched by doubleclicking a document.
>
> I think the right pattern to use here would be to set a flag in
>
On Wed, Sep 15, 2010 at 7:11 PM, Jerry Krinock wrote:
> Anything that I want to happen before a document opens, in case the app is
> launched by doubleclicking a document.
I think the right pattern to use here would be to set a flag in
-applicationDidFinishLaunching: or some later point. Until t
On 2010 Sep 15, at 18:58, Kyle Sluder wrote:
> There's no runloop running yet when -applicationWillFinishLaunching:
> is called…
Thank you, Kyle. Good explanation.
> Among other things, AppKit's automatically-installed autorelease pool hasn't
> been installed yet,
> Then NSRunAlertPanel is goi
On Wed, Sep 15, 2010 at 6:07 PM, Jerry Krinock wrote:
> - (void)applicationWillFinishLaunching:(NSNotification*)aNotification {
> NSRunAlertPanel(@"Hello",
> @"A crash is coming soon.",
> @"OK",
> nil,
> nil) ;
> }
The
Last week I found that an app would crash if I displayed a modal dialog in
-applicationWillFinishLaunching (note: *Will*), *and* *then* ran a modal
session on a window in -applicationDidFinishLaunching: (note: *Did*).
I've now reproduced it in a very simple demo, shown below. Why does this cras