Hacker News new | ask | show | jobs
by khedoros1 3216 days ago
A finger touching and leaving would be a high-priority event for the controller to output, and it should probably internally monitor events at a high resolution.

For position, as reported to the OS: what use would actually need a report every 2 milliseconds? Intuitively, I'd think that motions that matter wouldn't need that many datapoints to reliably differentiate.

2 comments

Remember that 500 interrupts per second isn't the same as a report every 2 milliseconds - reading status from a device may involve more than one interrupt.
True. And for some kinds of work, input latency probably becomes noticeable on a subconscious level quicker than one would guess.
It's often used to compensate for the fact that you want an up-to-date reading at arbitrary points within a frame. If you only update once per frame, and some code reads the position just before that every frame, that's going to give a full extra frame of lag, rather than just an extra 2ms.