Lines Matching +full:button +full:- +full:up

1 .. _joystick-api:
7 :Author: Ragnar Hojland Espinosa <ragnar@macula.net> - 7 Aug 1998
18 driver now reports only any changes of its state. See joystick-api.txt,
27 the driver provides up to 32.
57 		__u8 number;    /* axis/button number */
65 -------------
69 	#define JS_EVENT_BUTTON         0x01    /* button pressed/released */
74 events on open. That is, if it's issuing an INIT BUTTON event, the
86 ---------------
88 The values of ``number`` correspond to the axis or button that
90 is, you have both an axis 0 and a button 0). Generally,
108 --------------
110 For an axis, ``value`` is a signed integer between -32767 and +32767
115 For a button, ``value`` for a press button event is 1 and for a release
116 button event is 0.
137 snippet, this ends up being shorter.
141 -------------
145 task of detecting double clicks, figuring out if movement of axis and button
161 	b) open the device in non-blocking mode (O_NONBLOCK)
165 ----------
167 If read returns -1 when reading in O_NONBLOCK mode, this isn't
170 all events on the queue (that is, until you get a -1).
208  events. You can increment this size bumping up JS_BUFF_SIZE in
219 In this case, read would return -1 if the queue was empty, or some
245 -------------
247 JSIOGCVERSION is a good way to check in run-time whether the running
249 IOCTL will fail. For a compile-time decision, you can test the
257 ----------
259 JSIOCGNAME(len) allows you to get the name string of the joystick - the same
271 -------------
314 		int buttons;    /* immediate button state */
331 except that the values are non-negative. The 1.2.8+ drivers use a