-
-
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
ERROR: hotkey: xxx is registered #19
Comments
I think this is a known issue, see #11 |
So this means that there is no solution currently? Sorry I am far from familiar with native terms, so hard to understand the conclusion from the linked issue |
The reason for having this error is that someone else had registered this hotkey combination already. To solve it, guarantee the key combination does not conflict with others. I think @ventsislav-georgiev worked on potential solutions before, but we have not converged to a satisfactory solution yet. |
So this means that if some app, somewhere somehow assigned a key bind and this app is not even active anymore / not listening for key use, this lib won't be able to use this shortcut anyway? Because I am assigning completely "random" shortcut making sure it is not used (when I use it nothing happens), it still returns an error |
I think if you already grabbed the combination for your application successfully, future registration won't impact your registration anymore. I don't entirely sure how you did random shortcuts, but I am pretty confident that some combination will work. Otherwise, it should be a system issue rather than the library itself. |
Actually it was totally my bad, I was misusing the library - instantiating it in the wrong place of execution :) Thank you for your help though! |
I am trying to use this library with
wails
GUI library and everytime I get the error message that a hotkey is registeredno matter which key I am using with any modifier
not even sure where to look for some additional debuggin info, would you have any advice / help?
The text was updated successfully, but these errors were encountered: