Lines Matching refs:joystick

36     0xFD            joystick report (both sticks)
37     0xFE            joystick 0 event
38     0xFF            joystick 1 event
106 In this mode, the ikbd generates a record whenever the joystick position is
107 changed (i.e. for each opening or closing of a joystick switch or trigger).
109 The joystick event record is two bytes of the form:
117 The current state of the joystick ports may be interrogated at any time in
120 The ikbd response to joystick interrogation is a three byte report of the form
121     0xFD                ; joystick report header
130 time to reporting the state of the joystick ports at a user specifiable rate.
147 The ikbd may be commanded to translate the use of either joystick into the
149 velocity joystick cursor.
177 either axis and the Y=0 origin at the top of the screen, and joystick event
178 reporting mode for joystick 1, with both buttons being logically assigned to
179 the mouse. After any joystick command, the ikbd assumes that joysticks are
367 joystick events are also queued.
389 joystick switch or trigger causes a joystick event record to be generated.
396 INTERROGATE commands to sense joystick state.
417 time-of-day clock, and monitor the joystick. The rate sets the interval
418 between joystick samples.
442     TX                  ; length (in tenths of seconds) of joystick closure
445     TY                  ; length (in tenths of seconds) of joystick closure
448     VX                  ; length (in tenths of seconds) of joystick closure
451     VY                  ; length (in tenths of seconds) of joystick closure
455 In this mode, joystick 0 is scanned in a way that simulates cursor keystrokes.
469 Disable the generation of any joystick events (and scanning may be internally
470 disabled). Any valid joystick mode command resumes joystick monitoring. (The
471 joystick mode commands are SET JOYSTICK EVENT REPORTING, SET JOYSTICK
585             0x94    joystick mode
588             0x9A    joystick enable/disable