AutoHotkey Community

[jmh]

There seems to be a problem using a menu with a hotstring (v1.0.18).
The hotstring is called, not the menu. The following code demonstrates:

Menu amenu, add, anitem

::ahotstring::
MsgBox ahotstring
return

^m::Menu amenu, Show

anitem:
MsgBox anitem
return

The message box displays "ahotstring", with "anitem" not displayed at all.
The only way around it seems to be to create a dummy hotstring that simply returns.

Jason.

[Chris]

I ran the example you posted and it seems to work as expected and as documented. Can you verify by trying the example exactly as posted?

If there's still a problem, please let us know.

[jmh]

I copied that code from a test script in the first place. But anyway, after
copying the posted code to a new script, I still get the same result:
press ^m to bring up the menu, select "anitem" and "ahotstring" is called,
not "anitem". Am I missing something?

Jason <jadoxa @ yahoo.com.au>

[Chris]

That's strange (I still get the correct result on my system). Are you using v1.0.18? Which OS?

To help isolate this, you might try it on a different PC if you have easy access to one.

[Guest]

Not another computer, but I dual boot XP/98, so I tried in 98 and it did
indeed work correctly. After going through all my startup programs I
discovered it to be a problem with Barclock. The weird thing is, it only
happens on startup - if it's loaded manually immediately after startup,
or exited and restarted, then AutoHotkey works fine. Since I'm probably
the only person using Barclock, there's nothing to worry about.

[Chris]

Thanks for following up on that.