[GH-ISSUE #306] Feature Request: Show trackpad clicks when tap-to-click is enabled #260

New issue

Open

opened 2026-05-05 05:10:23 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 05:10:23 -06:00

Owner

Originally created by @gurjeet on GitHub (Sep 7, 2024).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/306

Thank you for implementing the "Show Mouse Clicks" feature! It is very useful.

One of the first things I change on a now macos machine is to enable tap-to-click (System Settings > Trackpad > Tap to click). So, instead of having to hard press on the trackpad for a click, I can use light taps to click on things. But these taps are not shown by Keycastr.

So, for my screen recordings to show where I am clicking, I have to either (a) remember to hard-press on trackpad, or (b) disable tap-to-click feature for the duration of the recording. I'd prefer to use the second workaround.

It would be nice to not have to use the workaround, and have Keycastr automatically show click actions when tap-to-click is enabled.

Thank you for the great utility! 🙏

Originally created by @gurjeet on GitHub (Sep 7, 2024). Original GitHub issue: https://github.com/keycastr/keycastr/issues/306 Thank you for implementing the ["Show Mouse Clicks"](https://github.com/keycastr/keycastr/issues/168) feature! It is very useful. One of the first things I change on a now macos machine is to enable tap-to-click (System Settings > Trackpad > Tap to click). So, instead of having to hard press on the trackpad for a click, I can use light taps to click on things. But these taps are not shown by Keycastr. So, for my screen recordings to show where I am clicking, I have to either (a) remember to hard-press on trackpad, or (b) disable tap-to-click feature for the duration of the recording. I'd prefer to use the second workaround. It would be nice to not have to use the workaround, and have Keycastr automatically show click actions when tap-to-click is enabled. Thank you for the great utility! 🙏

gitea-mirror added the

enhancement

compatibility

labels 2026-05-05 05:10:23 -06:00

gitea-mirror commented

2026-05-05 05:10:27 -06:00

Author

Owner

@akitchen commented on GitHub (Sep 7, 2024):

Thank you for opening an issue about this - I've wanted to better differentiate different click/tap gestures but haven't been able to put much thought into it lately.

I tested this and noticed that tap-to-click does still send the click event, but it's often too quick for the visualizer around the mouse pointer to animate it (it is representing mouse down and mouse up, and these happen too quickly for the animation). If you try to slow down your tap just a bit you may see a faint animation. These events do still show in the visualizer if you have that option enabled.

I'll have to look at whether there are tweaks to the animation or other things which could help avoid not seeing these events around the pointer.

@akitchen commented on GitHub (Sep 7, 2024): Thank you for opening an issue about this - I've wanted to better differentiate different click/tap gestures but haven't been able to put much thought into it lately. I tested this and noticed that tap-to-click does still send the click event, but it's often too quick for the visualizer around the mouse pointer to animate it (it is representing mouse down and mouse up, and these happen too quickly for the animation). If you try to slow down your tap just a bit you may see a faint animation. These events do still show in the visualizer if you have that option enabled. I'll have to look at whether there are tweaks to the animation or other things which could help avoid not seeing these events around the pointer.

gitea-mirror commented

2026-05-05 05:10:30 -06:00

Author

Owner

@theviking commented on GitHub (Dec 5, 2025):

+1 on this. Would be great for demoing navigation capabilities between different input devices

@theviking commented on GitHub (Dec 5, 2025): +1 on this. Would be great for demoing navigation capabilities between different input devices