- From: Jim (JR) <notifications@github.com>
- Date: Wed, 12 Jan 2022 03:44:19 -0800
- To: w3c/gamepad <gamepad@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 12 January 2022 11:44:32 UTC
@reillyeon Ref: [https://w3c.github.io/gamepad/#other-events](https://w3c.github.io/gamepad/#other-events) I don't see much to comment on here except for the fact that they say it "requires more discussion". My two kopeks: At least initially, a generic gamepad event that returns the entire gamepad data-frame (gamepad dictionary?) would be sufficient. (Ref: KISS rule) As far as data processing is concerned, we should be concentrating on getting the ***DATA*** to the developer/application. : Any additional data-massaging can be done to the returned data on the server or within the JavaScript on the client.. (*i.e* Qualifying axis inputs with a button press, normalizing or constraining data, etc.) After that has been implemented, the question of ***adding*** additional gamepad events can be addressed based on need. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/gamepad/pull/152#issuecomment-1010956833 You are receiving this because you are subscribed to this thread. Message ID: <w3c/gamepad/pull/152/c1010956833@github.com>
Received on Wednesday, 12 January 2022 11:44:32 UTC