Lines Matching full:of
13 In order to utilize the full power of the new multi-touch and multi-user
17 drivers to report details for an arbitrary number of contacts.
19 The protocol is divided into two types, depending on the capabilities of the
22 devices capable of tracking identifiable contacts (type B), the protocol
32 Contact details are sent sequentially as separate packets of ABS_MT
33 events. Only the ABS_MT events are recognized as part of a contact
35 applications, the MT protocol can be implemented on top of the ST protocol
39 input_mt_sync() at the end of each packet. This generates a SYN_MT_REPORT
44 input_mt_slot(), with a slot as argument, at the beginning of each packet.
46 prepare for updates of the given slot.
48 All drivers mark the end of a multi-touch transfer by calling the usual
51 of events/packets.
54 type B slot protocol lies in the usage of identifiable contacts to reduce
55 the amount of data sent to userspace. The slot protocol requires the use of
60 enumeration of the full set of anonymous contacts currently on the
66 Creation, replacement and destruction of contacts is achieved by modifying
67 the ABS_MT_TRACKING_ID of the associated slot. A non-negative tracking id
71 the full state of each initiated contact has to reside in the receiving
73 attribute of the current slot.
77 contact that is reported by the hardware. Whenever the identity of the
81 a BTN_TOOL_*TAP event to inform userspace of the total number of contacts
88 total number of type B slots reported in the absinfo for the ABS_MT_SLOT axis.
90 The minimum value of the ABS_MT_SLOT axis must be 0.
106 The sequence after moving one of the contacts looks exactly the same; the
122 If the driver reports one of BTN_TOUCH or ABS_PRESSURE in addition to the
156 message removes the association of slot 0 with contact 45, thereby
169 A set of ABS_MT events with the desired properties is defined. The events
171 minimum set consists of ABS_MT_POSITION_X and ABS_MT_POSITION_Y, which
174 of the contact area and approaching tool, respectively.
178 glass. You will see two regions, one inner region consisting of the part
179 of the finger actually touching the glass, and one outer region formed by
180 the perimeter of the finger. The center of the touching region (a) is
181 ABS_MT_POSITION_X/Y and the center of the approaching finger (b) is
188 instead. Devices capable of contact hovering can use ABS_MT_DISTANCE to
213 In addition to the MAJOR parameters, the oval shape of the touch and finger
215 and MINOR are the major and minor axis of an ellipse. The orientation of
217 direction of the finger ellipse is given by the vector (a - b).
219 For type A devices, further specification of the touch shape is possible
235 The length of the major axis of the contact. The length should be given in
237 possible value of ABS_MT_TOUCH_MAJOR is sqrt(X^2 + Y^2), the diagonal [#f4]_.
240 The length, in surface units, of the minor axis of the contact. If the
244 The length, in surface units, of the major axis of the approaching
245 tool. This should be understood as the size of the tool itself. The
246 orientation of the contact and the approaching tool are assumed to be the
250 The length, in surface units, of the minor axis of the approaching
255 the notion of pressure. The fingers of the hand and the palm all have
260 of TOUCH and WIDTH for pressure-based devices or any device with a spatial
269 The orientation of the touching ellipse. The value should describe a signed
270 quarter of a revolution clockwise around the touch center. The signed value
272 the Y axis (north) of the surface, a negative value when the ellipse is
278 Touch ellipsis are symmetrical by default. For devices capable of true 360
280 indicate more than a quarter of a revolution. For an upside-down finger,
286 not (uniquely) any values in between. In such cases, the range of
290 The surface X coordinate of the center of the touching ellipse.
293 The surface Y coordinate of the center of the touching ellipse.
296 The surface X coordinate of the center of the approaching tool. Omit if
301 The surface Y coordinate of the center of the approaching tool. Omit if the
305 The four position values can be used to separate the position of the touch
306 from the position of the tool. If both positions are present, the major
311 The type of approaching tool. A lot of kernel drivers cannot distinguish
322 contact. The sequence of points forms a polygon which defines the shape of
329 [#f5]_. The value range of the TRACKING_ID should be large enough to ensure
330 unique identification of a contact maintained over an extended period of
338 The flora of different hardware unavoidably leads to some devices fitting
343 cannot be obtained. Assuming X and Y are the lengths of the sides of the
351 The range of ABS_MT_ORIENTATION should be set to [0, 1], to indicate that
372 Rationale: We have no information about the orientation of the touching
381 The process of finger tracking, i.e., to assign a unique trackingID to each
383 problem. At each event synchronization, the set of actual contacts is
384 matched to the set of contacts from the previous synchronization. A full
391 In the specific application of creating gesture events, the TOUCH and WIDTH
393 between index finger and thumb. With the addition of the MINOR parameters,
395 and with ORIENTATION, one can detect twisting of fingers.
405 subsequent events of the same type refer to different fingers.
408 .. [#f2] The list can of course be extended.