AutoHotkey Community

[schandl]

I posted the following problem in the support section and some possible solutions were found. But I still wonder if this is the intended behaviour. Here is some example code:

[Laszlo]

In my XP laptop Win-x is not defined by the OS, therefore it behaves as x alone. With your script, Win-y does not disable it, so I get an x, but no MsgBox. It looks strange, I agree.

[Chris]

The tilde prefix makes the hotkey use the keyboard hook. Since the hook is designed to ignore simulated keystrokes for the purposes of triggering hotkeys, the tilde prevents Send #x from triggering the Win+x hotkey.

The hook ignores simulated keystrokes to prevent infinite loops wherein a hotkey triggers itself endlessly. Although this behavior is by design, I'll try to clarify it in the help file, perhaps under ListHotkeys or #UseHook.

To work around this, you can simply Gosub a hotkey rather than triggering it with a keystroke:

#y::
Gosub ~#x
return

[schandl]

Thanks for the explanation, Chris. Your solution works, but only if Win+x is defined as in the exmaple. It does not work if it was defined using the Hotkey command. Oh well, I think I have to look into a work-around for the script I am trying to extend.

Thanks anyway
Bernd

[Chris]

When using the hotkey command to define #x, have the #y hotkey do a Gosub to the label you assigned to #x.

[toralf]

Hi, Chris
I think the script schandl wants to extend uses the "A_Hotkey" variable. So he wants #x to be executed, so the rest of the script works without changes. Right?

But you could extend the routine. Set a status variable when #y is pressen, and in the routine that is called via #x you insert a if statement that tests that status variable and uses it to use someting else then "A_Hotkey".
_________________
Ciao
toralf

[schandl]

Toralf, you are right. But by now I decided to adapt the whole script to my needs instead of trying to extend using some weird hack. This will also help to learn a little more about AutoHotkey.

Bernd