- From: Jake Archibald <notifications@github.com>
- Date: Thu, 04 Jan 2018 09:10:01 -0800
- To: w3c/gamepad <gamepad@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 4 January 2018 17:10:25 UTC
@luser > One thing that might make this slightly awkward for the common use case in games is that AIUI most game loops have a process input / update state phase and a render phase. Currently most JS code I've seen just mashes those both into an rAF callback, handling input and updating state first, then rendering. Doesn't this proposal make this a bit more formal? You'd use the events as a place to update state, then queue a rAF for the render phase. -- 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-355340478
Received on Thursday, 4 January 2018 17:10:25 UTC