Re: Premature notification from NSApplication - workaround?
Re: Premature notification from NSApplication - workaround?
- Subject: Re: Premature notification from NSApplication - workaround?
- From: Keary Suska <email@hidden>
- Date: Mon, 21 Apr 2008 09:40:58 -0600
- Thread-topic: Premature notification from NSApplication - workaround?
on 4/21/08 8:14 AM, email@hidden purportedly said:
> I'm responding to: - (void) applicationDidBecomeActive:
> (NSNotification*) aNotification
>
> But when I get the notification, it seems that [NSApp mainWindow]
> still returns nil as if it were inactive. The message is obviously
> sent before -mainWindow is set up, which means that in fact the
> application isn't really yet active in a useful sense - the message is
> sent prematurely.
>
> Any way to get the current main window at this time?
I assume that it is this way to allow for click-thrus, so if your app has
more than one window open, a user could click on a window that wasn't
previously main, and make it so.
If you know that you will only every have one main window, you could
remember it when -applicationDidResignActive: is called.
Otherwise you may be able to call a handler method with
performSelectr:afterDelay:.
HTH,
Keary Suska
Esoteritech, Inc.
"Demystifying technology for your home or business"
_______________________________________________
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