Re: [w3c/gamepad] Make gamepads accessible by web worker (#37)

Thanks for getting back to me, @marcoscaceres, this was an old enough thread I wasn't sure discussion would still be in play at all.  With the benefit of having more sleep and the calmness that comes from having your code start working I can say that- although I have misgivings and dread about the *how*- I do have the SharedArrayBuffer working smoothly for the moment. (using temp vars to hold input on the DOM so that I only access the buffer once per index per animation frame, DOM-side)  I am uncertain if that will hold once I get to implementing an audio worklet, but that is another day's problem. :)

As to polled inputs vs events, #8 is interesting.  I will read through it and some others more thoroughly as spare time allows.  From my perspective the two issues overlap heavily enough as to be the same, and I share the same misgivings I saw in a skim of in the thread about spammy events like "GamepadAxis" and "GamepadGyro".  Spammy events.  I'd imagine they will cause similar issues to what I was experiencing with dropped events while sending keyboard event data to SharedArrayBuffer, which in turn will make Worker access even more important.

I will direct any future commentary I have on the subject of events to that thread, however, to keep things on topic.  Thanks again! :)

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

Message ID: <w3c/gamepad/issues/37/1820059458@github.com>