Re: Quit menu item undimming itself?!
Re: Quit menu item undimming itself?!
- Subject: Re: Quit menu item undimming itself?!
- From: Nir Soffer <email@hidden>
- Date: Wed, 10 May 2006 10:17:02 +0300
On 10/05/2006, at 02:30, John Stiles wrote:
Heh, you're right. I switched from a sheet to a window recently and
that's when this became an issue at all. I said "sheet" in a prior
description of my app, but that was inaccurate; it's just a window
now. It used to be a sheet ;) In older builds, when it was a sheet, it
worked exactly like you describe it. It was kind of cool.
You can run a modal session for that window too, see runModalForWindow:
FWIW, I used to handle this by beeping and returning NO in
applicationShouldTerminate, but some other members of our team, as
well as our testers, agreed that if a menu item is just going to beep
at you, it should probably be dimmed. Personally I found this to be a
compelling argument and so I ended up going down this road :)
Beeping when the user choose quit is evil, and telling him to cancel
the operation and quit again is even worse, because you can provide a
"Cancel Operation" button in that dialog. The user may force-quit your
app, leaving your important operation in some undefined state.
Questioning my design isn't really an appropriate response here.
Please try to be helpful.
Questionable design should be questioned, its helpful. I even googled
for you to provide a helpful link. I apologize if that was not enough
:-)
Best Regards,
Nir Soffer
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden