hotkey, parser bug ?

[Zelio]

Maybe it is me, but I don't understand how work the parser, I hope my examples will be explicit

everything normal, triggering order then overwrite (ź hide ž and Ź hide Ž)

Code: Select all

<+<!z::Ź
<!z::ź
<^<+<!z::Ž
<^<!z::ž

bug at line "+!z::Ź" because ź hide Ź, something wrong with "both" after "left" side? why "+!z" triggers and doesn't overwrite "!z" hotkey or send Ź?

Code: Select all

<^<+<!z::Ž
<^<!z::ž
+!z::Ź
!z::ź

fix1 : to use same "side" then use "<"

Code: Select all

<^<+<!z::Ž
<^<!z::ž
<+<!z::Ź
!z::ź

fix2 : to use send

Code: Select all

<^<+<!z::Ž
<^<!z::ž
+!z::send Ź
!z::ź

fix3 : priority up (parser), unlogic, and a new bug

Code: Select all

+!z::Ź
!z::ź ; other bug ? ź don't hide ž
<^<+<!z::Ž
<^<!z::ž

[lexikos]

There's nothing wrong with the parser, but there is some ambiguity in the keyboard hook's hotkey recognition. The main problem with your script is probably that you are using remappings, not hotkeys (except +!z::send Ź, which is a hotkey). Remappings implicitly use the wildcard modifier, as shown in the documentation. You can use ListHotkeys to verify this.

[Zelio]

Oh ok, thank, will you fix this ambiguity ?
I thought, wildcare modifier or not, if I sort them in the right order, to play with logic and overwrite by triggering first matched.
... also it was not for me, http://ahkscript.org/boards/viewtopic.php?f=5&t=2103

[lexikos]

I was able to work around it by sorting them in the right order...