mirror of
https://github.com/keycastr/keycastr.git
synced 2026-10-23 08:07:30 -06:00
[GH-ISSUE #337] Default visualiser doesn't work on macOS Tahoe, Svelte works #288
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#288
Loading…
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 @carlos-algms on GitHub (Jan 17, 2026).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/337
I just installed KeyCastr today and added it to
PrivacyandInputsecurity options, restarted it and the keys were not being displayed.When I switch from the default Visualiser to
Svelte, I can see it, and it works as expected.If I switch back to
default, it disappears and shows no keys.I changed no other option, other than the Visualiser.
@carlos-algms commented on GitHub (May 14, 2026):
It strikes again!
Today, it disappeared.
I had to switch the layout from
defaulttoSveltemultiple times to make it appear.Svelteseems to be the only working layout.@akitchen commented on GitHub (May 14, 2026):
This is not related to macOS Tahoe. Either the visualizer is off screen (possibly due to changing monitors/displays layout) or it is not receiving events for various reasons. Even with the privacy options enabled in the settings app, if a foreground app or device management profile is using secure key entry then KeyCastr will not receive full keystrokes, only modifier key events.
If you are confident that it's not a problem with secure key entry, you can reset the app's settings with
defaults delete io.github.keycastrin the terminal.@carlos-algms commented on GitHub (May 14, 2026):
Why would Svelte work then?
@akitchen commented on GitHub (May 14, 2026):
The different visualizers store their positions separately. So it's possible for the default visualizer to be offscreen while svelte isn't.
You can use svelte to help diagnose this - do you see all keystrokes, or only modifiers? If showing only modifiers, then something is limiting full keystrokes and the default visualizer may not show anything. If svelte is showing all keys successfully then the default visualizer is almost certainly offscreen. Resetting is the easiest remedy, or if you have access to a large monitor, changing your displays layout may help you find its position.
@carlos-algms commented on GitHub (May 14, 2026):
Ok, I ran the delete command, and I realised the "Normal" layout doesn't have borders. 😞