Lines Matching refs:contact

15 objects in direct contact with the device surface, is needed.  This
33 events. Only the ABS_MT events are recognized as part of a contact
38 Drivers for type A devices separate contact packets by calling
41 contact and prepare to receive another.
43 Drivers for type B devices separate contact packets by calling
65 identified contact, and use that slot to propagate changes for the contact.
68 is interpreted as a contact, and the value -1 denotes an unused slot. A
71 the full state of each initiated contact has to reside in the receiving
77 contact that is reported by the hardware. Whenever the identity of the
78 contact associated with a slot changes, the driver should invalidate that
95 Here is what a minimal event sequence for a two-contact touch would look
110 Here is the sequence after lifting the first contact::
117 And here is the sequence after lifting the second contact::
125 zero-contact event reaching userland.
131 Here is what a minimal event sequence for a two-contact touch would look
144 Here is the sequence after moving contact 45 in the x direction::
150 Here is the sequence after lifting the contact in slot 0::
156 message removes the association of slot 0 with contact 45, thereby
157 destroying contact 45 and freeing slot 0 to be reused for another contact.
159 Finally, here is the sequence after lifting the second contact::
174 of the contact area and approaching tool, respectively.
186 than unity, is related to the contact pressure. For pressure-based devices,
187 ABS_MT_PRESSURE may be used to provide the pressure on the contact area
188 instead. Devices capable of contact hovering can use ABS_MT_DISTANCE to
189 indicate the distance between the contact and the surface.
235 The length of the major axis of the contact. The length should be given in
240 The length, in surface units, of the minor axis of the contact. If the
241 contact is circular, this event can be omitted [#f4]_.
246 orientation of the contact and the approaching tool are assumed to be the
254 the contact. The ratio ABS_MT_TOUCH_MAJOR / ABS_MT_WIDTH_MAJOR approximates
259 The pressure, in arbitrary units, on the contact area. May be used instead
268 The distance, in surface units, between the contact and the surface. Zero
269 distance means the contact is touching the surface. A positive number means
270 the contact is hovering above the surface.
320 instead use input_mt_report_slot_state(). A contact's ABS_MT_TOOL_TYPE may
326 contact. The sequence of points forms a polygon which defines the shape of
327 the contact. This is a low-level anonymous grouping for type A devices, and
332 The TRACKING_ID identifies an initiated contact throughout its life cycle
334 unique identification of a contact maintained over an extended period of
386 initiated contact on the surface, is a Euclidian Bipartite Matching