-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
[bug] keybindings override system shortcuts #211
Comments
@roloit can you attach a video of the bug? I can't reproduce it on my end (macos Monterrey). |
So first I start playing something, hide the window, then click the force quit shortcut while the application is hidden, it quits the application, it's very annoying when you try to quit other apps, and first, muffon quits, only then you can quit the application you're in. macOS Sequioa |
Hmm.... I'll check the code for just-in-case. For confirmation @roloit : you're holding down |
Found the bug, no need to worry. Thank you for the report. I'll go ahead and report this. @roloit this will be fixed in the next version. We apologize for the inconvenience caused.
@staniel359 @gamersi this registers a globalShortcut, meaning the shortcut will be registered system-wide. In this case |
I definitely was outside of muffon. |
Note: You don't have to wait for official releases. Our beta program offers facilities for testing the fixes (e.g., v2.1.0 had 23 beta tests). What you can do:
TL;DR Wait for us to fix this issue, enroll in the beta program and use the beta until we declare the fix stable. I do not see an official release coming in the next 8 weeks. But betas are quite frequent. |
Weird thing now, probably a bug? On macOS, if I click play, then hide the window, go to another application/tab, and try to force quit the application (Say I'm in a browser, decide to force quit it with shortcut, muffon is hidden), instead of the application I'm in to quit, muffon quits, and it happens even if I don't have any windows open... It happens in version 2.1.0, version 2.0.3 doesn't have that issue.
The text was updated successfully, but these errors were encountered: