Lines Matching full: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
232 The INPUT_PROP_DIRECT property indicates that device coordinates should be
245 considered undefined and the device type should be deduced in the
251 pressing down on the pad causes a button click, this property should be
263 touchpads, the semi-mt property should be set.
282 the primary button press. BTN_{MIDDLE,RIGHT,4,5,etc.} should be used to report
283 further buttons of the device. REL_WHEEL and REL_HWHEEL should be used to report
291 contact. BTN_TOOL_<name> events should be reported where possible.
293 For new hardware, INPUT_PROP_DIRECT should be set.
301 location of the touch. BTN_TOUCH should be used to report when a touch is active
302 on the trackpad. Where multi-finger support is available, BTN_TOOL_<name> should
305 For new hardware, INPUT_PROP_POINTER should be set.
311 should be used to report when the tool is in contact with the tablet.
312 BTN_{STYLUS,STYLUS2} should be used to report buttons on the tool itself. Any
318 For new hardware, both INPUT_PROP_DIRECT and INPUT_PROP_POINTER should be set.