-
-
Notifications
You must be signed in to change notification settings - Fork 14
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]: App Auto-Switching Bug (Additional Details Included) #82
Comments
This happens to me too. If I have Firefox and Lightroom open, opening KeyClu with the hot key in Lightroom and then releasing it will switch to Firefox, then doing the same in Lightroom will switch back to Firefox. I've also had it try to display the non-existent hotkeys for the hidden loginwindow even though Firefox is showing active menus up in my menubar. Using cask installed 0.26 on 14.5. |
Hey jhlimdev, |
Oh, thanks for noticing issue. Simply restart the app, and the update should go through. |
#82 App auto switching problem still persists. And When I reboot my Mac, keyclu does not open automatically. So I have to manually click the app icon. I love other features you added on this update! |
Thanks for the report. I'll keep working on the issue. |
Description
Hi there!
Thank you for making such a great app!
I’m here to report a bug.
As a temporary solution, I go to the Keyclu settings and toggle any feature, such as “Silent Launch/quit,” off and then on again.
p.s. If you turn on the stage manager, you can see this bug more properly. And I tried uninstalling it using Homebrew or manually deleting it (when installed from a .dmg file), but it didn’t work.
Expected behavior
When pressing the Command key twice and holding it to bring up Keyclu, the current app should not switch to another app after releasing the Command key. The focus should remain on the current app until the user manually switches to another app.
App version
0.26(22630)
macOS version
macOS Sonoma 14.5
Installation method
Manual (dmg/zip)
Checklist before submitting a bug
The text was updated successfully, but these errors were encountered: