Lines Matching refs:motion

49 The ikbd can report mouse motion in three distinctly different ways. It can
50 report relative motion, absolute motion in a coordinate system maintained
51 within the ikbd, or by converting mouse motion into keyboard cursor control
60 button being pressed or released, or motion in either axis exceeding a
61 settable threshold of motion. Regardless of the threshold, all bits of
65 relative mouse motion events will be generated: (a) while the keyboard has
79 If the accumulated motion before the report packet is generated exceeds the
80 +127...-128 range, the motion is broken into multiple packets.
92 The ikbd can translate mouse motion into the equivalent cursor keystrokes.
94 each axis. The ikbd internally maintains mouse motion information to the
97 Mouse motion produces the cursor key make code immediately followed by the
151 for the appropriate cursor motion keys. The trigger or fire buttons of the
232 generated asynchronously by the ikbd whenever motion exceeds the setable
249 between 0 and large positive numbers. Excess motion below 0 is ignored. The
259 Set mouse monitoring routines to return cursor motion keycodes instead of
260 either RELATIVE or ABSOLUTE motion records. The ikbd returns the appropriate
262 either axis. When the keyboard is in key scan code mode, mouse motion will
264 command is not affected by the mouse motion origin.
327 mouse motion. This causes mouse motion toward the user to be negative in sign
335 system within the ikbd for all relative or absolute mouse motion. (DEFAULT)
336 This causes mouse motion toward the user to be positive in sign and away from
353 disabled). Any valid mouse mode command resumes mouse motion monitoring. (The
368 Mouse motion should be accumulated while the output is paused. If the ikbd is
369 in RELATIVE MOUSE POSITIONING REPORTING mode, motion is accumulated beyond the
372 causes any accumulated motion to be immediately queued as packets, if the