Re: [w3c/gamepad] Add a model section (PR #220)

@nondebug commented on this pull request.



> +      <p>
+        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, ordered such that
+        earlier [=touch points=] appear closer to the start of the [=list=]. 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>
+        representing its position along the user's left-right axis and a

When we describe the thumbstick axes we use both Horizontal and Left/Right, let's do the same here to minimize ambiguity.

I think there's another issue here, aligning to the horizontal axis only makes sense if the touchpad is on the top/bottom/front/back of the gamepad. If it's on the left or right side then the left/right axis is perpendicular to the surface of the touchpad. To make this generic we should define the coordinate system for any orientation.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/pull/220#discussion_r2061137220
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/gamepad/pull/220/review/2795710243@github.com>