Re: [Audacity-devel] Key bindings and accelerator keys in keyboard prefs

[Leland <le...@au...>]

On 09.10.2013 15:53, Gale (Audacity Team) wrote:
> Leland wrote:
>> So, when I started fiddling around with the keyboard prefs, I wondered
>> why there wasn't an accelerator assigned to the "Set" button.  Couldn't
>> figure it out so assigned one while I was assigning for the new controls.
>>
>> I've just figured out why...
>>
>> Select any entry in the tree/name view and then get over to the hotkey
>> edit control.  Press "ALT+S" to assign to that entry.  What just happened
>> is that not only did ALT+S get added to the hotkey control, but it was
>> also set in the view above.
>>
>> The reason is that the ALT+S accelerator was executed as soon as you
>> pressed the keys and this is not what is desired.  This will happen with
>> any of the accelerators on that window.
> ...
>> Now, on Windows, I can (fairly easily) make the hotkey edit control
>> accept any key combo and have it ignore the accelerator IF the hotkey
>> edit control has the focus.  Otherwise the accelerators would work as
>> normal.
>>
>> I can't do that on GTK without some difficulty and even that is only an
>> untest idea at this point.
>>
>> On Mac...again...I have no idea.
>>
>> So, the question to y'all...
>>
>>   Is it worth it to try and prevent the accelerators for executing while
>> the hotkey edit control has focus?
> I don't think it's a problem at all on Mac - as far as I know, accelerators
> are irrelevant to that platform, at least those using ALT or Option. So if
> you hold Option - D while in the shortcut edit box, you don't default all
> your shortcuts as pressing ALT + D would do on Windows and Linux.
>
> Although this is rarely complained of, I think it's worth investigating if
> you
> can prevent accelerators activating in the shortcut edit box.
Easy to do on Windows...I'm not going to attempt it on GTK unless 
complaints come in.

And I'll just forget about the Mac for this one.  :-)

> While TABbing out of the edit box works fine for those used to keyboard
> navigation, it's not uncommon for users to press their desired shortcut
> combo, then hit ENTER and wonder why their shortcut wasn't set. So
> I think David's idea of a non-empty Edit box making the Set button the
> temporary default is useful.
The problem with that is "RETURN" and "NUMPAD_ENTER" are assignable as 
shortcuts and are currently assigned to "Toggle Focused Track".

Leland