AutoHotkey Community

Hello,

on a german system the Hotkey-Control stores "ZIRKUMFLEX" for the Key "^". Also the "+"-Key is stored as "+" what means Shift for AHK. Is there a way to handle this limitations?

Tekl

Thanks for reporting this. It should definitely be fixed, perhaps in one of the following ways:

1) Make the key names produced by a Hotkey control symbolic (single character) so that they will be compatible with the Hotkey command. If there is no symbol, it would use the English name.

2) Make the hotkey command capable of understanding native language key names.

I will research this and try to find the best compromise between functionality and backward compatibility.

By the way, the plus key problem is a separate issue because making "+" a hotkey requires the SCnnn hotkey method on keyboard layouts whose "+" does not require the shift key. This is a known limitation for which there is not yet a workaround.

Hi Chris,

making symbolic characters would be no solution because "Zirkumflex" is "^", the symbol for Ctrl. So it should produce SCxxx also for "+". Maybe if + is alone it's SCxxx and if it is ++ then +SCxxx and so on.

What about an alternative way to catch Hotkeys? I'm trying around with Input, but till now it's not perfect: http://www.autohotkey.com/forum/viewtopic.php?t=4704

Maybe a special command could help:

GetHotkeyString, Variable, Restriction

Tekl

In today's v1.0.37.03, hotkeys should now recognize the following symbols as valid key names: #!^+$<>*~

For example, ^+ would be Control-Plus and ## would be Win-PoundSign.

I think this indirectly fixes most of the issues with the Hotkey control. However, the ZIRCUMFLEX issue is still not fixed because there's no obvious way to fix it for all such keys (perhaps dead keys always yield native language names). Until some solution is discovered, it's probably best to have your script explicitly translate ZIRCUMFLEX into the symbol ^.

That's an interesting idea but would likely be complex to implement. Therefore, I've put it in with the other improvements planned for the Input command.

Thanks.

To avoid confusion, would it be preferable to introduce single-character variables to insert in a hotkey-call strucutre ?

%Sharp = #
or %Sharp := "#"

#%Sharp::Run, something ; Win + Sharp character

Of course the notation is also a proposition...

I thought about adding new key names, but supporting the symbols directly seemed like it would be more intuitive to most people.

May be my proposition can be seen like a possible notation alternative.
Thanks for your answer.

I reread your post and now I understand your proposal. Unfortunately, the current architecture and syntax of the program would make it difficult to support dynamic hotkeys in that fashion. You probably know that the Hotkey command can create hotkeys dynamically.

That's true !!!

I was thinking that this type of notation could be ambigous.
But after reading with more attention, I'm OK it is not the case...
^++ = Ctrl-Shift +
!! = Alt !

P.S : In a far future (not a high priority), it would be good to be able to have dynamic hotkeys if it's possible...

Thanks for all your work

Hi Nemroth,

I don't understand why you don't want to use the hotkey-command for dynamic hotkeys.

Tekl

At first I didn't understand well the Chris's proposition As I said in the post before, I re-read and its OK.
For the Hotkey command, I forgot about it as I never use it (at least for the moment), but I have plans to use it in the near future to allow the user of the script I am creating to create it's own hotkeys

So no problem, Tekl.