Lines Matching refs:motion

59 The ikbd can report mouse motion in three distinctly different ways. It can
60 report relative motion, absolute motion in a coordinate system maintained
61 within the ikbd, or by converting mouse motion into keyboard cursor control
71 button being pressed or released, or motion in either axis exceeding a
72 settable threshold of motion. Regardless of the threshold, all bits of
76 relative mouse motion events will be generated: (a) while the keyboard has
91 If the accumulated motion before the report packet is generated exceeds the
92 +127...-128 range, the motion is broken into multiple packets.
106 The ikbd can translate mouse motion into the equivalent cursor keystrokes.
108 each axis. The ikbd internally maintains mouse motion information to the
111 Mouse motion produces the cursor key make code immediately followed by the
173 for the appropriate cursor motion keys. The trigger or fire buttons of the
267 generated asynchronously by the ikbd whenever motion exceeds the setable
287 between 0 and large positive numbers. Excess motion below 0 is ignored. The
300 Set mouse monitoring routines to return cursor motion keycodes instead of
301 either RELATIVE or ABSOLUTE motion records. The ikbd returns the appropriate
303 either axis. When the keyboard is in key scan code mode, mouse motion will
305 command is not affected by the mouse motion origin.
383 mouse motion. This causes mouse motion toward the user to be negative in sign
394 system within the ikbd for all relative or absolute mouse motion. (DEFAULT)
395 This causes mouse motion toward the user to be positive in sign and away from
418 disabled). Any valid mouse mode command resumes mouse motion monitoring. (The
436 Mouse motion should be accumulated while the output is paused. If the ikbd is
437 in RELATIVE MOUSE POSITIONING REPORTING mode, motion is accumulated beyond the
440 causes any accumulated motion to be immediately queued as packets, if the