-
Notifications
You must be signed in to change notification settings - Fork 10
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
Hotkey Dialog implement key stroke capturing #251
Comments
I have no clue about Python. So I can't judge this approach (but first idea sounds worth exploring it.)
In AHK you simply could use the "Suspend" command to deactivate and activate the hotkeys. Other programs still will be affected (But maybe it is good to notice that a hotkey is already in use). |
Well, the UI is Qt for Python. Python using Qt is a little like AHK is using other DLLs in a more sophisticated way ;] About |
Did you try "Suspend, off" global and "Suspend, permit" in a subroutine. Never use it, but thought it should work :) |
No, didn't try. I would need a way to tell the runtime to do that from the UI. And thats not the idea of a2 :) We would just shutdown the runtime and reload it. But actually: we could add this functionality to the tray menu of a2 🤔 I mean as it was once an ac'tivAid option there. But I dunno... is that needed? I never used that functionality if I could just unload and reload. |
Makes sense. I rarely use "suspend" and I could probably had used pause as well in these cases. So you may leave it out until someone complains. I doubt that many users need this. Have an uncluttered menu is important as well. |
Current Behavior
There is the "Hotkey Dialog" and you can only Click the buttons that should be captured. The (super old) "simple dialog" just offers to type the combinations.
Expected Behavior
@Cyberklabauter in #250 suggested to have the simple dialog accept actual key compbinations like Ctrl+D for instance. You actually press it and it takes exactly that key.
bla
Well, I would really like the ability to do that but I don't like the idea to have it in the simple dialog only. 🤔
In would consider the ability to see what's actually free and what not to be rather important! If you don't know you might actually already trigger something that you might not want. I mean ... there are things we could do to mitigate that and some other ideas we could have implemented:
(this widget is not really "new" to Qt but I think I didn't have it when a2 was first created ;])
The a2ui is actually not Autohotkey itself so we could not look at
A_ThisHotkey
directly. Let's have a look how this Qt widget performs. We could also talk to the Qt devs if something is missing and fix it ourselves. If all breaks we can of course have an extrea Autohotkey script looking and the pressed keys on the dialog (e.g. like the coords field is done with coordinates picking)I mean I'd try it without this first and if it's really bad we could try that.
The text was updated successfully, but these errors were encountered: