Lines Matching refs:joystick

44     0xFD            joystick report (both sticks)
45     0xFE            joystick 0 event
46     0xFF            joystick 1 event
122 In this mode, the ikbd generates a record whenever the joystick position is
123 changed (i.e. for each opening or closing of a joystick switch or trigger).
125 The joystick event record is two bytes of the form::
135 The current state of the joystick ports may be interrogated at any time in
138 The ikbd response to joystick interrogation is a three byte report of the form::
140     0xFD                ; joystick report header
150 time to reporting the state of the joystick ports at a user specifiable rate.
169 The ikbd may be commanded to translate the use of either joystick into the
171 velocity joystick cursor.
202 either axis and the Y=0 origin at the top of the screen, and joystick event
203 reporting mode for joystick 1, with both buttons being logically assigned to
204 the mouse. After any joystick command, the ikbd assumes that joysticks are
435 joystick events are also queued.
460 joystick switch or trigger causes a joystick event record to be generated.
470 INTERROGATE commands to sense joystick state.
497 time-of-day clock, and monitor the joystick. The rate sets the interval
498 between joystick samples.
528     TX                  ; length (in tenths of seconds) of joystick closure
531     TY                  ; length (in tenths of seconds) of joystick closure
534     VX                  ; length (in tenths of seconds) of joystick closure
537     VY                  ; length (in tenths of seconds) of joystick closure
541 In this mode, joystick 0 is scanned in a way that simulates cursor keystrokes.
558 Disable the generation of any joystick events (and scanning may be internally
559 disabled). Any valid joystick mode command resumes joystick monitoring. (The
560 joystick mode commands are SET JOYSTICK EVENT REPORTING, SET JOYSTICK
692             0x94    joystick mode
695             0x9A    joystick enable/disable