Re: [Audacity-quality] Unable to assign unicode characters as shortcut

[Robert H. <aar...@gm...>]

2015-08-26 12:59 GMT+02:00, David Bailes <drb...@gm...>:
> On Tue, Aug 25, 2015 at 8:10 PM, Robert Hänggi <aar...@gm...>
> wrote:
>
>> Hello again
>>
>> There's another strange thing I've stumbled upon.
>>
>> Apart from the reassignments mentioned above, I do also assign the a
>> key to "Amplify".
>> I can do that but the key is already assigned to "Previous Tool" and I
>> press OK in order to overwrite it.
>> However, "A" is now assigned to both commands and what's even more
>> queer, I can't clear it from "Previous Tool".
>>
>> Any ideas?
>>
>
> thanks for spotting the problem - in fact there were other connected
> problems as well.
> I think there was just a line of code in the wrong place, so I've committed
> a fix. You should now be able to clear the shortcut from "previous tool",
> and the duplicates shouldn't happen again (I think).
>
> David.
>
>
>> Robert

Thanks a bunch David.
Seems to be fixed.

-rjh
>>
>>
>> 2015-08-24 22:36 GMT+02:00, David Bailes <drb...@gm...>:
>> > On Mon, Aug 24, 2015 at 5:41 PM, Leland <le...@au...>
>> > wrote:
>> >
>> >>
>> >>
>> >> > -----Original Message-----
>> >> > From: David Bailes [mailto:drb...@gm...]
>> >> > Sent: Monday, August 24, 2015 11:22 AM
>> >> > To: audacity-quality <aud...@li...>
>> >> > Subject: Re: [Audacity-quality] Unable to assign unicode characters
>> >> > as
>> >> > shortcut
>> >> >
>> >> > On Mon, Aug 24, 2015 at 3:35 PM, Leland <le...@au...
>> >> > <mailto:le...@au...> > wrote:
>> >> >
>> >> >
>> >> >       Okay Robert.  Give it a try in the next nightly (unless you're
>> >> building
>> >> > yourself).  Again, it will not work with previously assigned
>> shortcuts,
>> >> so you'll
>> >> > have to remap any that used Unicode keys.
>> >> >
>> >> >
>> >> >
>> >> > (I'm not Robert, but) I can confirm that it works nicely here - you
>> >> > even
>> >> get the
>> >> > shortcut characters that you expect in the edit box, and in the list
>> of
>> >> > shortcuts.
>> >> >
>> >> > Am I right in thinking that this works because wxwidgets
>> incorrectly(?)
>> >> gives
>> >> > the unicode value rather than the keycode in this case? A rare case
>> >> > of
>> >> > a
>> >> sort
>> >> > of error being useful?
>> >> >
>> >> I actually think they planned it this way.
>> >
>> >
>> > Yes, it's meant to work for latin-1 keys.
>> >
>> > from manual:
>> > GetKeyCode()
>> > <
>> http://docs.wxwidgets.org/trunk/classwx_key_event.html#a3dccc5a254770931e5d8066ef47e7fb0
>> >
>> > should
>> > be used to handle special characters (such as cursor arrows keys or
>> > HOME
>> or
>> > INS and so on) which correspond to wxKeyCode
>> > <
>> http://docs.wxwidgets.org/trunk/defs_8h.html#a41c4609211685cff198618963ec8f77d
>> >
>> > enum
>> > elements above the WXK_START constant. While GetKeyCode()
>> > <
>> http://docs.wxwidgets.org/trunk/classwx_key_event.html#a3dccc5a254770931e5d8066ef47e7fb0
>> >
>> > also
>> > returns the character code for Latin-1 keys for compatibility, it
>> > doesn't
>> > work for Unicode characters in general and will return WXK_NONE for any
>> > non-Latin-1 ones.
>> >
>> > David.
>> >
>> >
>> >>   I tried it on OSX as well, and while I get a different key code
>> >> there
>> >> (as expected), it is still consistent across the keydown/char/up
>> >> events.
>> >>
>> >> Leland
>> >>
>> >>
>> >>
>> >>
>> >>
>> ------------------------------------------------------------------------------
>> >> _______________________________________________
>> >> Audacity-quality mailing list
>> >> Aud...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>> >>
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Audacity-quality mailing list
>> Aud...@li...
>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>>
>