AutoHotkey Community

Hi,
why does the following AHK-Script produce the warning mentioned in the subject when pressing "x"?



I use AutoHotkey v1.0.48.05.L61 and Windows 7 64bit.

you need to drop this:

Then it should work.

I'm not sure if this is a bug - you're getting the error message because the hotkey code is triggering the hotkey, and causing an infinite loop. I would simply put the hook on the first instance of the hotkey:

quoteing from here http://www.autohotkey.com/docs/commands ... Active.htm


Soo... If the Notepad/WordPad window is not up, it doesn't use the other hotkey. So what popurse does it have to make a hot key to send its self.
Short answer, DONT PUT IT THERE.

@gamax92
The line

should not send the hotkey to itself, since I used the modifier symbol "$". However it does send the hotkey to itself if there are also the lines

which actually shouldn't have any effect at all unless there's a certain window active.

@a4u
The code you presented is another form of the bug. Actually your code should trigger a warning message, since

is a self-triggering Hotkey. However, for any strange reasons, the warning message does not occur if there are the additional lines

I know that. I actually had that problem once and figured if i take the line out, the message would go away. It still acts like its there.

Where's your Return?

_________________
"Read the manual. Read it again. Search the forum.
Try something before asking. Show what you've tried."

Antonio França
My stuff: Google Profile

By itself - yes. However, I put a Hook on the first instance of the x-hotkey. If you want to argue that that hook shouldn't matter because it's in an #If-directive, you might have a good point. Also note, you could switch the order of the hotkey definitions, as long as the first hotkey definition has the hook:

@MasterFocus
Returns are not necessary, since the hotkey definitions comprise each only a single line. If you prefer, you may insert Returns; it doesn't affect the bug..

@a4u
Yes, the bug is that autohotkey evaluates the modifier of only one (the first) hotkey definition ignoring the fact that the two definitions are in different contexts (#directive).

Hi,

could someone from the development section please confirm that this is a bug and provide some information as to whether or not there will be efforts to fix it.

Thanx,
HjP

This isn't a bug this is just badly written code.
The code you wrote was probably giving a error because the first x hotkey would run and trigger the "send x". Which would cause a infinite loop thus causing that error to appear.

You should of done:

If you use ListHotkeys with HjP's original script, it will show a single reg hotkey:

There are two reasons for this:

1. $ must be applied to the first instance of the hotkey.
   
2. #IfWin causes the keyboard hook to be used only if it is necessary. That is, the keyboard hook is normally required to decide whether the keystroke should be passed through to the system. Since in this case there is a global, non-suspended variant of the hotkey, it will necessarily never be passed through to the system, so the keyboard hook is not required.

The second hotkey is a single line hotkey. The first hotkey is not, since there is no command to the right of "::". It is similar to the following, which specifies multiple criteria for a single hotkey:

The following change has been made in v1.1.00.01:

Now if any instance of the hotkey has $ or #UseHook, it applies to all instances of that hotkey.