Lines Matching +full:multi +full:- +full:protocol
1 .. _input-event-codes:
8 The input protocol uses a map of types and codes to express input device values
18 The input protocol is a stateful protocol. Events are emitted only when values
36 - Used as markers to separate events. Events may be separated in time or in
37 space, such as with the multitouch protocol.
41 - Used to describe state changes of keyboards, buttons, or other key-like
46 - Used to describe relative axis value changes, e.g. moving the mouse 5 units
51 - Used to describe absolute axis value changes, e.g. describing the
56 - Used to describe miscellaneous input data that do not fit into other types.
60 - Used to describe binary state input switches.
64 - Used to turn LEDs on devices on and off.
68 - Used to output sound to devices.
72 - Used for autorepeating devices.
76 - Used to send force feedback commands to an input device.
80 - A special type for power button and switch input.
84 - Used to receive force feedback device status.
92 ------
99 - Used to synchronize and separate events into packets of input data changes
106 - TBD
110 - Used to synchronize and separate touch events. See the
111 multi-touch-protocol.txt document for more information.
115 - Used to indicate buffer overrun in the evdev client's event queue.
121 ------
134 - These codes are used in conjunction with input trackpads, tablets, and
169 - These codes denote one, two, three, and four finger interaction on a
182 be used to emit these codes. Please see multi-touch-protocol.txt for details.
185 ------
196 - These codes are used for vertical and horizontal scroll wheels,
198 physical size of which varies by device. For high-resolution wheels
199 this may be an approximation based on the high-resolution scroll events,
206 - High-resolution scroll wheel data. The accumulated value 120 represents
207 movement by one detent. For devices that do not provide high-resolution
209 high-resolution scrolling, the value may be a fraction of 120.
211 If a vertical scroll wheel supports high-resolution scrolling, this code
213 and REL_HWHEEL may be an approximation based on the high-resolution
214 scroll events. There is no guarantee that the high-resolution data
219 ------
228 - Used to describe the distance of a tool from an interaction surface. This
233 - BTN_TOOL_<name> should be set to 1 when the tool comes into detectable
240 - Used to describe the state of a multi-value profile switch. An event is
246 - Used to describe multitouch input events. Please see
247 multi-touch-protocol.txt for details.
251 - For touch devices, many devices converted contact size into pressure.
259 pressure data is in arbitrary units. If the resolution is non-zero, the
265 -----
279 ------
288 - Used to report the number of microseconds since the last reset. This event
297 ------
303 ------
308 ------
314 -----
320 ------
334 --------------------------------------
338 transformations, such as scaling, flipping and rotating). Non-direct input
339 devices require non-trivial transformation, such as absolute to relative
341 drawing tablets; non-direct devices: touchpads, mice.
344 on the screen and thus requires use of an on-screen pointer to trace user's
345 movements. Typical pointer devices: touchpads, tablets, mice; non-pointer
353 --------------------
364 ------------------
380 -----------------------
394 ------------------------
406 The guidelines below ensure proper single-touch and multi-finger functionality.
407 For multi-touch functionality, see the multi-touch-protocol.rst document for
411 ----
419 ------------
429 ---------
436 on the trackpad. Where multi-finger support is available, BTN_TOOL_<name> should
442 -------