Re: applicationDidHide - Not Getting Triggered?
Re: applicationDidHide - Not Getting Triggered?
- Subject: Re: applicationDidHide - Not Getting Triggered?
- From: Jason Teagle <email@hidden>
- Date: Sat, 19 May 2012 10:46:19 +0100
- Organization: Organised Bytes Software
Hiding an app is a specific operation that's not related to quitting
> it or closing its last window. There's a Hide<App Name> menu item
>in the application menu (the one named after the application).
>
*That* is when -applicationDidHide: would be called.
Ah... so there is. My bad. All part of the learning process.
Closing the last window of an application doesn't automatically quit it
...
The app is still running and current. Its menu is shown in the menu bar
>and you can still use it.
This time I noticed that even though I'm running under the debugger,
there is an icon in the dock; the icon looks just like Interface
Builder's so I didn't realise it was mine!
This seems to be a problem though - clicking on it won't bring my main
window back. Am I supposed to respond to something here? As my app is
still running I assumed it would come back up automatically as if it had
simply been minimized rather than closed.
I realise there is a wealth of documentation out there so if I'm asking
questions that are better answered by reading something in particular,
please let me know. I've read quite a bit as I'm going along but it
looks like I should start reading up on app lifecycles. I had it easy
with the screensaver as the work was done for me - and on the iPhone it
'just worked'.
Under Lion, there can be a disconnect between the apparent running
state of your app and the real one. Lion may show an app as running
when its process has actually been terminated. It may also make it
> seem that an app which had no windows open and was not current has
> quit when it's actually still running. In the first case, resources
Assuming I don't specifically want to support any of this new behaviour
at this time (i.e., not actually *trying* to support it explicitly), are
there any implications for my app that I should be aware of to make sure
my apps are as future-proof as possible? Best practices that I should
get into the habit of right now, since I'm learning the ropes anyway? I
would hate to write a killer first app only to find it dies in flames or
is buggy as hell under Lion's new regime (I'm still only on Snow Leopard).
--
Jason Teagle
_______________________________________________
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