Skip to content
Discussion options

You must be logged in to vote

Trigger threshold is the right control, but its unit is not the one you are reasoning in, which is why turning it up did not behave the way you expected.

RelToBtnHandler.notify compares event.value — the delta carried by a single EV_REL report — against the threshold, and nothing accumulates between reports. So the test is "did this one report carry at least X counts", not "has the pointer travelled X since I started moving". In practice that makes it a gate on mouse speed rather than on distance: a small quick flick produces a large delta and trips it immediately, while a slow drag across the whole desk produces a stream of small deltas and never trips it at all. Your slight movements ar…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@Kzer-Za
Comment options

Answer selected by Kzer-Za
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants