- From: Bradley Needham <notifications@github.com>
- Date: Mon, 25 Jul 2022 12:29:41 -0700
- To: w3c/gamepad <gamepad@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/gamepad/pull/168/review/1049957991@github.com>
@bradleyneedham commented on this pull request. > + `touchData.touchID`. + </li> + <li>Set |touchEvent|.{{GamepadTouch/surfaceId}} to be + device surfaceId. + </li> + <li>Set |touchEvent|.{{GamepadTouch/position}}[0] to be + |normalizedX:float|. + </li> + <li>Set |touchEvent|.{{GamepadTouch/position}}[1] to be + |normalizedY:float|. + </li> + <li>Set |touchEvent|.{{GamepadTouch/surfaceDimensions}}[0] to be + device max x-axis coordinate. + </li> + <li>Set |touchEvent|.{{GamepadTouch/surfaceDimensions}}[1] to be + device max y-axis coordinate.<p>(<i>note: surfaceDimensions can be set to `null`</i>)</p> This may need more discussion. Perhaps there is not a case where surfaceDimensions can be null. For the DS4 touch coordinates are normalized using the device touch point and the surface dimensions. Should the algorithm include receiving input from a device that sends already normalized touch points and does not report surface dimensions? -- Reply to this email directly or view it on GitHub: https://github.com/w3c/gamepad/pull/168#discussion_r929226562 You are receiving this because you are subscribed to this thread. Message ID: <w3c/gamepad/pull/168/review/1049957991@github.com>
Received on Monday, 25 July 2022 19:29:54 UTC