[GH-ISSUE #210] On macOS 11+, input is temporarily lost when switching to menu bar only #176

New issue

Closed

opened 2026-05-05 05:03:56 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 05:03:56 -06:00

Owner

Originally created by @akitchen on GitHub (Jun 14, 2021).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/210

I've noticed that when I switch KeyCastr to display in Menu Bar only, the default visualizer stops receiving or displaying keystrokes. Once I bring up the preferences pane again then KeyCastr resumes.

There must be some kind of subtle change in macOS 11+; we may be able to work around this but it needs some investigation

Originally created by @akitchen on GitHub (Jun 14, 2021). Original GitHub issue: https://github.com/keycastr/keycastr/issues/210 I've noticed that when I switch KeyCastr to display in Menu Bar only, the default visualizer stops receiving or displaying keystrokes. Once I bring up the preferences pane again then KeyCastr resumes. There must be some kind of subtle change in macOS 11+; we may be able to work around this but it needs some investigation

gitea-mirror

2026-05-05 05:03:56 -06:00

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-05 05:04:02 -06:00

Author

Owner

@hanglearning commented on GitHub (Oct 24, 2021):

I am using macOS Bug Sur 11.5.2 (20G95) having the same issue.

@hanglearning commented on GitHub (Oct 24, 2021): I am using macOS Bug Sur 11.5.2 (20G95) having the same issue.

gitea-mirror commented

2026-05-05 05:04:04 -06:00

Author

Owner

@akitchen commented on GitHub (Feb 13, 2022):

I'm not yet sure this is something that can be fixed in KeyCastr -- it seems to temporarily stop receiving events from the OS in this case. It could even be a subtle bug in macOS.

@akitchen commented on GitHub (Feb 13, 2022): I'm not yet sure this is something that can be fixed in KeyCastr -- it seems to temporarily stop receiving events from the OS in this case. It could even be a subtle bug in macOS.

gitea-mirror commented

2026-05-05 05:04:06 -06:00

Author

Owner

@akitchen commented on GitHub (Oct 29, 2023):

I'm not sure this is a bug in KeyCastr or something that can be addressed. I've had trouble reproducing it recently, although I did notice some apps like Terminal can have secure keyboard entry permanently enabled, which prevents KeyCastr from receiving keyboard events

@akitchen commented on GitHub (Oct 29, 2023): I'm not sure this is a bug in KeyCastr or something that can be addressed. I've had trouble reproducing it recently, although I did notice some apps like Terminal can have secure keyboard entry permanently enabled, which prevents KeyCastr from receiving keyboard events