Re: [w3c/gamepad] Should fire events instead of using passive model (#4)

> Could a model like https://developer.mozilla.org/en-US/docs/Web/API/PointerEvent/getCoalescedEvents help here?

This sounds promising! Gamepad axis events are pretty similar to pointer move events: they're an analog input that can be highly variable (even if the user isn't touching an analog stick, it's likely to be changing just due to jitter).

I suspect that for most gamepad usecases the API that users want is "what state on the gamepad has changed since the last time I looked?" For button presses it's important to have a record of *every* pressed/released event so that you don't miss quick button presses, but for axes you probably just want the current value, but you probably want to know if it has changed.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/issues/4#issuecomment-355267301