Lines Matching refs:be

3 may be used.
23 type has a set of applicable codes to be used in generating events. See the
27   - Used as markers to separate events. Events may be separated in time or in
107     touchscreens. These devices may be used with fingers, pens, or other tools.
109     code should be set to a value of 1. When the tool is no longer interacting
110     with the input device, the BTN_TOOL_<name> code should be reset to 0. All
115     BTN_TOUCH is used for touch contact. While an input tool is determined to be
116     within meaningful physical contact, the value of this property must be set
120     certain value. BTN_TOUCH may be combined with BTN_TOOL_<name> codes. For
125 BTN_TOUCH must be the first evdev code emitted in a synchronization frame.
131 future, this distinction will be deprecated and the device properties ioctl
132 EVIOCGPROP, defined in linux/input.h, will be used to convey the device type.
138     BTN_TOOL_DOUBLETAP should be set to value 1 for the duration of the motion.
148 be used to emit these codes. Please see multi-touch-protocol.txt for details.
154 space is unknown. If the absolute position is known, EV_ABS codes should be used
172     event should only be emitted while the tool is hovering, meaning in close
174     the input device may be used freely in three dimensions, consider ABS_Z
203     should be coded as an uint32 value, which is allowed to wrap around with
232 management. Its usage is not well defined. To be addressed later.
238 types, additional information can be provided in the form of device
243 The INPUT_PROP_DIRECT property indicates that device coordinates should be
256 considered undefined and the device type should be deduced in the
262 pressing down on the pad causes a button click, this property should be
267 compatibility, both methods need to be checked in userspace.
274 touchpads, the semi-mt property should be set.
279 gestures can normally be extracted from it.
281 If INPUT_PROP_SEMI_MT is not set, the device is assumed to be a true MT
289 visual/haptic areas for left, middle, right buttons intended to be used
311 REL_{X,Y} must be reported when the mouse moves. BTN_LEFT must be used to report
312 the primary button press. BTN_{MIDDLE,RIGHT,4,5,etc.} should be used to report
313 further buttons of the device. REL_WHEEL and REL_HWHEEL should be used to report
318 ABS_{X,Y} must be reported with the location of the touch. BTN_TOUCH must be
320 BTN_{MOUSE,LEFT,MIDDLE,RIGHT} must not be reported as the result of touch
321 contact. BTN_TOOL_<name> events should be reported where possible.
323 For new hardware, INPUT_PROP_DIRECT should be set.
331 location of the touch. BTN_TOUCH should be used to report when a touch is active
333 be used to report the number of touches active on the trackpad.
335 For new hardware, INPUT_PROP_POINTER should be set.
339 BTN_TOOL_<name> events must be reported when a stylus or other tool is active on
340 the tablet. ABS_{X,Y} must be reported with the location of the tool. BTN_TOUCH
341 should be used to report when the tool is in contact with the tablet.
342 BTN_{STYLUS,STYLUS2} should be used to report buttons on the tool itself. Any
343 button may be used for buttons on the tablet except BTN_{MOUSE,LEFT}.
348 For new hardware, both INPUT_PROP_DIRECT and INPUT_PROP_POINTER should be set.