-
Notifications
You must be signed in to change notification settings - Fork 27
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
Long omni-key press don't work #416
Comments
It may have something to do with how your mouse handles the key-press. Some mice have "features" that repeatedly send a key-press if you're holding that key down. Check if you can disable that in your mouse software. If you're not using a special kind of mouse, maybe the key is just broken or semi-defective. Have you tried rebinding the omni-key to a different key? But be careful: don't bind it to a key that is used for chatting, as you may otherwise accidentally trigger something when typing a message. |
I tried rebinding it to a different key and it does the same thing |
I tried the "=" key and apply & restarted as you mentioned, the key worked it just bring the links to wiki over and over again |
Okay, I tried it. It seems there are a few keys where AutoHotkey can't tell if you're holding it or not. I'll try to find a workaround for that, but in the meantime you'll have to try a bunch of different keys. |
I tried with the "J" key as well but it keep doing the same things |
Okay, something is clearly wrong if that happens with regular letters as well. Have you changed any other setting in the hotkeys section of the tool? What kind of keyboard are you using, and does it use any software/drivers? Also, could you open the |
Not sure if you're still interested (since you stopped responding), but v1.54.6 includes some omni-key changes that might fix your issue. |
All features bound to a long omni-key press don't work.
I think what it does is when I long press on the omni-key it instead press the omni-key many times (the wiki shortcut keep popping over and over)
any suggestions?
The text was updated successfully, but these errors were encountered: