Re: applicationShouldTerminateAfterLastWindowClosed
Re: applicationShouldTerminateAfterLastWindowClosed
- Subject: Re: applicationShouldTerminateAfterLastWindowClosed
- From: Cameron Hayne <email@hidden>
- Date: Sat, 05 Oct 2002 18:06:34 -0400
On 5/10/02 5:38 pm, "Andrew Merenbach" <email@hidden> wrote:
>
applicationShouldTerminateAfterLastWindowClosed should be limited, as
>
users on the Mac OS do not generally expect their applications to quit
>
when the last window is closed.
This is true for document-centred applications.
>
I do have a question, though: what do
>
people usually do, then? One can disable the close button, for
>
example, but is that against the HIG, too?
I looked but I didn't see anything explicitly addressing this in the HIG. If
your app has one main window without which the app is useless, it would seem
better to me to leave the close button but make it quit the app. But if it
is conceivable that the user might benefit from your app even with the main
window closed (e.g. iTunes), then of course you should keep the app running
even with no windows.
>
Is it standard to hook up
>
the "New" File menu item in a non-document-based application to display
>
the main window?
Definitely not that! In fact, maybe it is not even necessary to have a File
menu at all in your case.
>
Or should we instead make a permanent window item in
>
the Windows menu, a la iTunes?
Yes - that seems to be the way it is usually done, although I haven't seen
it addressed in the HIG.
--
Cameron Hayne (email@hidden)
Hayne of Tintagel
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.