Re: [w3c/gamepad] Added touched property to GamepadButton (#26)

is it naive of me to suggest that a gamepad with built-in touchpad could/should be effectively treated as two separate inputs? on the one hand, the strictly gamepad side (buttons, sticks with axes, etc) which can be queried using the gamepad API, and on the other a touchpad, which is handled using the pointer events API?

i think the one pain point here would be if there are multiple gamepads, as there's currently no concept of assigning anything other than a unique ID for each pointer - assuming the touchpad is multitouch, you could end up with lots of pointers, all with their own unique ID, but no overarching "this belongs to one hand/single input/controller device" (and even if there were, marrying up any unique identifier for a gamepad to the unique identifier for the pointers would probably present further challenges).

---
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/pull/26#issuecomment-227513690

Received on Tuesday, 21 June 2016 17:34:33 UTC