Re: Controls & Key Equivalents

On Nov 22, 2010, at 8:06 PM, Kyle Sluder <[email protected]> wrote:

> On Mon, Nov 22, 2010 at 4:40 PM, Eric Gorr <[email protected]> wrote:
>> On Nov 22, 2010, at 7:31 PM, Kyle Sluder wrote:
>> 
>>> On Mon, Nov 22, 2010 at 4:24 PM, Eric Gorr <[email protected]> wrote:
>>>>> WHAT does your button DO?
>>>> 
>>>> I don't always know. But, perhaps, bring up another dialog.
>>> 
>>> Then nobody can answer the question.
>> 
>> One possible answer is to place the key-equivalent in a tooltip for the button.
> 
> No. Christiaan's whole point is that the answer depends on the context.

Using the tooltip to show the key equivalent is certainly an option.

> 
>> It will if it is on a dialog which the user visits.
> 
> That's not "elsewhere in the application" then.

It could be. Turn off a check box in a preference dialog and it could certainly affect functionality elsewhere in the application once the user dismissed the dialog.

Now, if that check box had a key equivalent, say cmd-e, to change it's state, how might you tell the user what that key equivalent is? Yes, I am aware that your answer is you wouldn't because the whole notion of key equivalents is obsolete.