[GH-ISSUE #296] Add an additional option to include navigation keys #251

New issue

Open

opened 2026-05-05 05:09:46 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 05:09:46 -06:00

Owner

Originally created by @akitchen on GitHub (Jun 9, 2024).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/296

This is covered across a few other issues, but it would be good to have an option to add navigation keys to the current display option. It could compose with "All Modified Keys" or "Command Keys Only".

I think this would include esc, tab/shift-tab, delete, arrows, numeric pad keys, spacebar, and return.

Originally created by @akitchen on GitHub (Jun 9, 2024). Original GitHub issue: https://github.com/keycastr/keycastr/issues/296 This is covered across a few other issues, but it would be good to have an option to add navigation keys to the current display option. It could compose with "All Modified Keys" or "Command Keys Only". I think this would include esc, tab/shift-tab, delete, arrows, numeric pad keys, spacebar, and return.

gitea-mirror added the

enhancement

label

2026-05-05 05:09:46 -06:00

gitea-mirror referenced this issue

2026-10-02 23:08:35 -06:00

[GH-ISSUE #251] Interoperability with python's keyboard library #212

gitea-mirror commented

2026-10-02 23:08:47 -06:00

Author

Owner

@AbdelrahmanHafez commented on GitHub (Aug 10, 2026):

Are you open for PRs for this? We can start with numpad keys (my main use-case here), and once we establish an accepted design we can tackle the rest.

@AbdelrahmanHafez commented on GitHub (Aug 10, 2026): Are you open for PRs for this? We can start with numpad keys (my main use-case here), and once we establish an accepted design we can tackle the rest.

gitea-mirror commented

2026-10-02 23:08:47 -06:00

Author

Owner

@akitchen commented on GitHub (Aug 10, 2026):

I appreciate the offer, but in this case - an update is coming soon which will launch the new minimal visualizer which will support this use case. And then the plan is to unify settings across the different visualizers as much as we can (it makes more sense to do that when there are three or more). Development has been slow but this is almost ready!

@akitchen commented on GitHub (Aug 10, 2026): I appreciate the offer, but in this case - an update is coming soon which will launch the new minimal visualizer which will support this use case. And then the plan is to unify settings across the different visualizers as much as we can (it makes more sense to do that when there are three or more). Development has been slow but this is almost ready!

gitea-mirror commented

2026-10-02 23:08:47 -06:00

Author

Owner

@AbdelrahmanHafez commented on GitHub (Aug 10, 2026):

Makes sense, I created the PR anyway and closed it immediately since I had prepared it yesterday already. Hopefully it'll help somehow with the new implementation.

Thanks for maintaining KeyCastr!

@AbdelrahmanHafez commented on GitHub (Aug 10, 2026): Makes sense, I created the PR anyway and closed it immediately since I had prepared it yesterday already. Hopefully it'll help somehow with the new implementation. Thanks for maintaining KeyCastr!