Re: Controls & Key Equivalents
Christiaan Hofman <[email protected]> Mon, 22 Nov 2010 23:47:04 +0100
| Newsgroups | gmane.comp.macosx.devel |
|---|---|
| Message-ID | <[email protected]> |
On Nov 22, 2010, at 23:25, Eric Gorr wrote: > Ok. > > Then, what solutions, if any, have you seen people use in modern cocoa applications? > For what? Seriously, you ask a generic question on which I have now answered several times that there is no generic answer (that's what "it depends" means). The ONLY specific context you have actually provided in your question is one that you have later said is not really the context. Also, "common functionality" is almost by definition NOT "app specific", so that sentence makes no sense to me. I made my point that if the functionality is common/not app specific/standard, you need do nothing. On the other hand when it is NOT common/standard/app specific, you probably shouldn't use key equivalents to begin with. Christiaan > > On Nov 22, 2010, at 5:18 PM, Christiaan Hofman wrote: > >> >> On Nov 22, 2010, at 23:04, Eric Gorr wrote: >> >>> >>> On Nov 22, 2010, at 4:59 PM, Christiaan Hofman wrote: >>> >>>> >>>> On Nov 22, 2010, at 22:42, Eric Gorr wrote: >>>> >>>>> One is allowed to assign key equivalents to controls like Push Buttons. >>>>> >>>>> For example, one might assign Cmd-P to push button. Would you make any attempt to let the user know that pressing Cmd-P is the same as clicking on that button? (Perhaps, via a tooltip, in the label of the control, etc.) Or, would you expect the user to learn about such equivalents in the documentation alone? >>>> >>>> That depends entirely on the situation. In particular how obvious the shortcut is. For instance, Enter for a default button, Escape for a Cancel button, Cmd-. for a stop button, Cmd-D for a "Don't" button are so common that they don't need explanation. Cmd-P should probably not be used as a key equivalent, as it is a standard shortcut for the Print menu item (though it would be acceptable for a Print button, in which case it would be clear.) >>> >>> Pretend it was some other letter that isn't common for some app specific functionality. >> >> That does not change my central answer: it depends (all the rest is illustration).