Lines Matching full:events

12 A single hardware event generates multiple input events. Each input event
14 used to separate input events into packets of input data changes occurring at
18 The input protocol is a stateful protocol. Events are emitted only when values
31 type has a set of applicable codes to be used in generating events. See the
36   - Used as markers to separate events. Events may be separated in time or in
99   - Used to synchronize and separate events into packets of input data changes
110   - Used to synchronize and separate touch events. See the
116     Client should ignore all events up to and including next SYN_REPORT
123 EV_KEY events take the form KEY_<name> or BTN_<name>. For example, KEY_A is used
126 emitted with value 0. Some hardware send events when a key is repeated. These
127 events have a value of 2. In general, KEY_<name> is used for keyboard keys, and
128 BTN_<name> is used for other types of momentary switch events.
140     code when events are generated.
170     purpose. A trackpad event generated by finger touches should generate events
183 EV_REL events describe relative changes in a property. For example, a mouse may
195     this may be an approximation based on the high-resolution scroll events,
210     scroll events. There is no guarantee that the high-resolution data
217 EV_ABS events describe absolute changes in a property. For example, a touchpad
236   - Used to describe multitouch input events. Please see
242 EV_SW events describe stateful binary switches. For example, the SW_LID code is
256 EV_MSC events are used for input and output events that do not fall under other
266     consecutive events is reliable on a reasonable time scale (hours).
274 EV_LED events are used for input and output to set and query the state of
280 EV_REP events are used for specifying autorepeating events.
285 EV_SND events are used for sending sound commands to simple sound output
291 EV_FF events are used to initialize a force feedback capable device and to cause
297 EV_PWR events are a special type of event used specifically for power
391 scroll wheel events where available.
399 contact. BTN_TOOL_<name> events should be reported where possible.
407 events like mice described above.
419 BTN_TOOL_<name> events must be reported when a stylus or other tool is active on