mirror of
https://github.com/keycastr/keycastr.git
synced 2026-05-15 14:15:50 -06:00
[GH-ISSUE #206] Whenever the "a" key is pressed, KeyCastr stops casting #174
Labels
No labels
bug
compatibility
discussion
documentation
enhancement
help wanted
help wanted
investigation needed
pull-request
release
visualizer
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/keycastr#174
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @izhang05 on GitHub (Jun 9, 2021).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/206
Whenever the "a" key is pressed, KeyCastr stops casting. This occurs even if the focus is on another application.
@gagregrog commented on GitHub (Jun 9, 2021):
I just installed keycastr and noticed the same. It appears that is the default keybind for start/stop casting. The default should probably be changed, but as an interim fix, you can bind a new hotkey from the preferences menu.
From the "General" tab, click in the "Toggle capturing:" box and then set a hotkey such as
cmd + opt + shift + aor similar, so it doesn't accidentally get triggered.@akitchen commented on GitHub (Jun 11, 2021):
Hmm, that's strange. It could be something with ShortcutRecorder, which desperately needs some updates for recent versions of macOS (note the incompatibility with dark mode too)
I'll add this to the list for the next release; thank you for opening an issue. And @RobertMcReed is right, hopefully you can reset this by setting a new shortcut.
@izhang05 commented on GitHub (Jun 12, 2021):
Thanks! Changing the shortcut worked.
@akitchen commented on GitHub (Jun 12, 2021):
I cleared out the user defaults for keycastr and did a fresh install, and the default shortcut on next run was set to ^⌥⌘K as expected. Please open another issue if you run into this again.