- From: Jake Archibald <notifications@github.com>
- Date: Sun, 31 Dec 2017 15:37:40 +0000 (UTC)
- To: w3c/gamepad <gamepad@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 31 December 2017 15:38:08 UTC
A similar option is a method where you declare which buttons & axis you're interested in, and it returns an `EventTarget` which fires a "change" event in the render steps of the event loop, and `getCoalescedEvents` gives you the full details. -- 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-354610162
Received on Sunday, 31 December 2017 15:38:08 UTC