- From: Matt Reynolds <notifications@github.com>
- Date: Thu, 12 Jun 2025 15:22:54 -0700
- To: w3c/gamepad <gamepad@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/gamepad/pull/220/review/2922799694@github.com>
@nondebug commented on this pull request. > + A [=gamepad=] may have [=touch surfaces=]. A <dfn>touch surface</dfn> + is an input control that provides 2D position data representing points + of contact. A [=gamepad=] has a <dfn>touch surface list</dfn> which is + a [=list=] containing the [=touch surfaces=] for the [=gamepad=]. The + list is ordered such that [=touch surfaces=] closer to the left side of + the [=gamepad=] appear closer to the start of the list. + </p> + <p> + A [=touch surface=] has an <dfn>active touch point list</dfn> [=input + value=], a [=list=] of zero or more [=touch points=] representing the + points of contact currently detected by the sensor. A <dfn>touch + point</dfn> represents a single point of contact at a single point in + time. A [=touch point=] has a <dfn>touch x coordinate</dfn> + and a <dfn>touch y coordinate</dfn> representing the position in the [=touch surface=]'s coordinate system. + If a [=touch surface=] is on the top, bottom, front, or back side of the [=gamepad=] then the [=touch x coordinate=] is measured along the left-right axis, otherwise it is measured along the top-bottom axis. + The [=touch y coordinate=] is measured along the perpendicular axis. We should, since the current spec is ambiguous about which way is +Y. For other axes we define this in the normalization steps, let's do the same for touch coordinates. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/gamepad/pull/220#discussion_r2143751897 You are receiving this because you are subscribed to this thread. Message ID: <w3c/gamepad/pull/220/review/2922799694@github.com>
Received on Thursday, 12 June 2025 22:22:58 UTC