Lines Matching refs:should

90     Client should ignore all events up to and including next SYN_REPORT
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
111     trackpads, tablets, and touchscreens should use at least one BTN_TOOL_<name>
138     BTN_TOOL_DOUBLETAP should be set to value 1 for the duration of the motion.
140     purpose. A trackpad event generated by finger touches should generate events
142     codes should have a value of 1 during any synchronization frame.
147 Note: In multitouch drivers, the input_mt_report_finger_count() function should
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
203     should be coded as an uint32 value, which is allowed to wrap around with
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
274 touchpads, the semi-mt property should be set.
292 If INPUT_PROP_TOPBUTTONPAD is set, userspace should emulate buttons
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
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
332 on the trackpad. Where multi-finger support is available, BTN_TOOL_<name> should
335 For new hardware, INPUT_PROP_POINTER should be set.
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
348 For new hardware, both INPUT_PROP_DIRECT and INPUT_PROP_POINTER should be set.