[GH-ISSUE #284] Display single "Ctrl", "Shift", "Option", and "Cmd" keys (if they are not pressed in combination with another key) #242

New issue

Open

opened 2026-05-05 05:09:12 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 05:09:12 -06:00

Owner

Originally created by @jmuheim on GitHub (Nov 30, 2023).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/284

This in some cases is very useful, for example when creating screencasts where one holds a single (or multiple) modifier keys WITHOUT a corresponding "other" key.

For example, when using a screen reader (NVDA in a Windows virtual machine), one can interrupt (cancel) the current output by pressing Control, or skip the current output line (and jump to the next line) by pressing Shift.

It would be great when KeyCastr would also display such key strokes. This could happen at the "keyUp" event of such a single key press.

What do you think? 👍

Originally created by @jmuheim on GitHub (Nov 30, 2023). Original GitHub issue: https://github.com/keycastr/keycastr/issues/284 This in some cases is very useful, for example when creating screencasts where one holds a single (or multiple) modifier keys WITHOUT a corresponding "other" key. For example, when using a screen reader (NVDA in a Windows virtual machine), one can interrupt (cancel) the current output by pressing Control, or skip the current output line (and jump to the next line) by pressing Shift. It would be great when KeyCastr would also display such key strokes. This could happen at the "keyUp" event of such a single key press. What do you think? 👍

gitea-mirror added the

enhancement

label 2026-05-05 05:09:12 -06:00

gitea-mirror commented

2026-05-05 05:09:17 -06:00

Author

Owner

@akitchen commented on GitHub (Feb 3, 2024):

This is a bit of a special case that might warrant a different visualizer. It's somewhat like what was being worked on in #203 but not exactly. But since you're talking about held keys, the visualizer idea in that PR is probably closer to what you're asking for than another modification to the default visualizer.

@akitchen commented on GitHub (Feb 3, 2024): This is a bit of a special case that might warrant a different visualizer. It's somewhat like what was being worked on in #203 but not exactly. But since you're talking about held keys, the visualizer idea in that PR is probably closer to what you're asking for than another modification to the default visualizer.

gitea-mirror commented

2026-05-05 05:09:20 -06:00

Author

Owner

@DanCates commented on GitHub (Apr 9, 2024):

This is a bit of a special case that might warrant a different visualizer. It's somewhat like what was being worked on in #203 but not exactly. But since you're talking about held keys, the visualizer idea in that PR is probably closer to what you're asking for than another modification to the default visualizer.

Hi! I'm just starting to use Keycastr and I immediately came to this PR because it appears that Keycastr's "Command keys only" option doesn't work for all the modifier keys, but only those combined with Command. This is strange as I am using Keycastr to show the keyboard shortcuts I am using as I work and record training videos. I'm assuming this is an extremely common use for the program. However, with "Command keys only" selected, it only seems to work consistently with keyboard shortcuts that start with or include the Command key. But there are many many shortcuts that use modifiers that don't include the Command key. Why are these not supported?

For instance, I use Amethyst as a window manager. It's default shortcuts use the modifiers Option + Shift + [letters]. None of these display when I'm using Keycastr because I have the "Command keys only" option selected, however I believe these easily fit the same intended use behind the "Command keys only" option. Can we update this functionality to include any modifiers?

Am I misunderstanding this functionality? Or are there disadvantages to the functionality when working with non-command modifier key combinations--explaining why this isn't already implemented?

Without this, the app's usefulness is greatly diminished but otherwise, it's fantastic.

@DanCates commented on GitHub (Apr 9, 2024): > This is a bit of a special case that might warrant a different visualizer. It's somewhat like what was being worked on in #203 but not exactly. But since you're talking about held keys, the visualizer idea in that PR is probably closer to what you're asking for than another modification to the default visualizer. Hi! I'm just starting to use Keycastr and I immediately came to this PR because it appears that Keycastr's "Command keys only" option doesn't work for all the modifier keys, but only those combined with Command. This is strange as I am using Keycastr to show the keyboard shortcuts I am using as I work and record training videos. I'm assuming this is an extremely common use for the program. However, with "Command keys only" selected, it only seems to work consistently with keyboard shortcuts that start with or include the Command key. But there are many many shortcuts that use modifiers that don't include the Command key. Why are these not supported? For instance, I use Amethyst as a window manager. It's default shortcuts use the modifiers Option + Shift + [letters]. None of these display when I'm using Keycastr because I have the "Command keys only" option selected, however I believe these easily fit the same intended use behind the "Command keys only" option. Can we update this functionality to include any modifiers? Am I misunderstanding this functionality? Or are there disadvantages to the functionality when working with non-command modifier key combinations--explaining why this isn't already implemented? Without this, the app's usefulness is greatly diminished but otherwise, it's fantastic.

gitea-mirror commented

2026-05-05 05:09:22 -06:00

Author

Owner

@akitchen commented on GitHub (Jun 9, 2024):

@DanCates those keystrokes you've described aren't command keys. But displaying all modified keystrokes is supported in the latest release.

This issue is actually about single presses of the modifier keys. These keys work a little differently within the eventing system and so some additional adjustments are needed, but I do agree it would be worthwhile. I'll be looking into it more when time permits.

@akitchen commented on GitHub (Jun 9, 2024): @DanCates those keystrokes you've described aren't command keys. But displaying all modified keystrokes is supported in the latest release. This issue is actually about single presses of the modifier keys. These keys work a little differently within the eventing system and so some additional adjustments are needed, but I do agree it would be worthwhile. I'll be looking into it more when time permits.

gitea-mirror commented

2026-05-05 05:09:23 -06:00

Author

Owner

@ryan-fabrikant commented on GitHub (Aug 27, 2025):

@akitchen thanks for creating and supporting a great product.

Wanted to +1 this feature request. I'm using Keycastr to record products that use command keys to toggle functionality, or as modifier keys that change the mouse cursor behavior on a canvas. These command keys aren't used in conjunction with another keystroke, but used by themselves.

@ryan-fabrikant commented on GitHub (Aug 27, 2025): @akitchen thanks for creating and supporting a great product. Wanted to +1 this feature request. I'm using Keycastr to record products that use command keys to toggle functionality, or as modifier keys that change the mouse cursor behavior on a canvas. These command keys aren't used in conjunction with another keystroke, but used by themselves.