-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hotstrings don't work when running alongside another AutoHotkey instance #20
Comments
It looks like this bug only appears when a normal Autohotkey script with at least one Hotstring is running. Example script
If this script is running, Hotstrings in Autohotkey.py do not work. If this script is suspended (or exited) the do work fine. A normal Autohotkey script without any Hotstring does not cause this error. I hope this helps to fix this bug. |
Hello @e-r-n-i-e! I believe here's what happens:
You should get the same result if instead of AutoHotkey.py you run the following regular AutoHotkey script alongside :SI:hw::Hello World Here are a few workarounds you could do:
Other options that require changes in AutoHotkey.py:
|
BTW I didn't think about using the constants like |
You are right, I get the same result using But I still would call it a bug, because it does not work as (I) expected. I would expect the following scripts to behave equally even when they are running both at the same time (or with another script using keyboard hooks):
This behaviour is caused by The Autohotkey documentation says:
I was able to get the expected behaviour for hotstrings without the
I leave it to you to find the right spot to really fix this. ;-) |
When I start the following script with
py -m ahkpy hello-world.py
the hotkey[Ctrl+Shift+H]
works as expected but both hotstrings don't. When typinghw
followed by a space the space is ommited but nothing else happens. When typingwtf
followed by a space the space is replaced byHello World
which results inwtfHello World
.hello-world.py:
I'm using Autohotkey 1.1.33.10 and Python 3.11.1 on Windows 10.
The text was updated successfully, but these errors were encountered: