mirror of
https://github.com/keycastr/keycastr.git
synced 2026-05-15 14:15:50 -06:00
[GH-ISSUE #228] Next features for mouse click visualization #192
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#192
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 @akitchen on GitHub (Feb 22, 2022).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/228
Following the release of v0.9.12, more improvements are planned around the visualization of mouse events:
@Zackhardtoname commented on GitHub (Apr 11, 2022):
I am mostly worried that my background is sometimes white and sometimes black.
@tryggvigy commented on GitHub (May 10, 2022):
Chrome sometimes uses two colors (blue and white) for
outlinefor this exact reason. Perhaps this technique can help here@ylluminate commented on GitHub (Jun 7, 2022):
Screenium 3 has some nice visualization functionality for mouse/cursor capture that could be emulated:

@akitchen commented on GitHub (Oct 29, 2023):
v0.9.14 will add basic support for displaying mouse events in the current visualizer but the ability to independently customize mouse click display color will have to wait for another release.
@akitchen commented on GitHub (Nov 19, 2024):
The click visualization started out as trying to match what QuickTime does when screen recording. It's the same radius and stroke width, more or less. The idea of two colors makes sense though, or maybe an alternate color for when the UI is in Dark Mode.
Our main use case is screen casting, so I don't think different colors for different kinds of clicks makes the most sense since it is non-obvious to the observer. Plus, it could be an accessibility concern for those who don't perceive colors as well as others. I'd probably prefer some kind of iconography or other indication of the click type or scroll action, like a small icon or glyphs displayed near the mouse click visualizer. Something like "Display button names" above, but nicer.
I wonder if @porg or @QuintB or any other UX community members have thoughts on this?
@porg commented on GitHub (Nov 19, 2024):
Thanks for considering my advice, I feel flattered. I will give it a thought and then share it here.
@theviking commented on GitHub (Dec 5, 2025):
Would it be possible to differentiate left, right, and wheel clicks? Currently the visualizer shows the same graphic for each
@ghost commented on GitHub (Jan 22, 2026):
Oh yes, this would be an awesome addition - differentiate left/right/middle/wheel clicks!
As it is now, the viewer can't really tell which exact mouse button am I pressing.
@LY1806620741 commented on GitHub (Mar 2, 2026):
why do not show scroll action?
Sometimes I need to tell them that I moved two fingers on the touchpad.