- From: Florian Bösch <notifications@github.com>
- Date: Wed, 03 Jan 2018 12:27:54 +0000 (UTC)
- To: w3c/gamepad <gamepad@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 3 January 2018 12:28:25 UTC
On Tue, Jan 2, 2018 at 12:36 PM, Jake Archibald <notifications@github.com> wrote: > > - If an axis or button changes value, an axischange/buttonvaluechange > event will fire in the render steps of the event loop. > > Please be aware that if you opportunistically fire events for changed axes, and you as a programmer react to those events immediately, you will experience unintended behavior, such as drawing a staircase instead of a diagonal line (because the X event fires first, at which time the Y value isn't available yet, and so forth). -- 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-355000565
Received on Wednesday, 3 January 2018 12:28:25 UTC