But it is still unclear to me *why* you want to do this. If your panel
has a close box, and it is the window with keyboard focus, many users
are going to expect Command-W to close that window. Going out of your
want to disable that functionality is likely to frustrate these users.
An example of this is in the Finder. The info window you get with
Command-I responds to Command-W. But the info inspector panel that
you get with Command-Option-I does not, despite having a close
button and being able to have focus. This drives me nuts, because I
often hit Command-W in the latter case and end up closing my Finder
file-browser window by mistake instead of the info panel.
(In case anyone's wondering: Command-Option-I toggles the info
inspector, so you can use that instead of Command-W.)
I do a graphic program and most users are used to the behavior of
adobe apps. There palettes have a close button but do not react on
command-w.
For me it is more logical that all windows with a "big" title bar
react on keyboard close commands and all panels with a "small" title
bar not.
Georg
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
