Lines Matching refs:you

14 (JS_EVENT_INIT) that you can read to check the initial state of the
37 If the read is successful, it will return sizeof(e), unless you wanted to read
56 If you choose not to differentiate between synthetic or real events
57 you can turn off the JS_EVENT_INIT bits
67 is, you have both an axis 0 and a button 0). Generally,
85 representing the position of the joystick along that axis. If you
87 full range, you should recalibrate it (with, for example, jscal).
98 may work well if you handle JS_EVENT_INIT events separately,
107 is much safer since it can't lose sync with the driver. As you would
124 If you open the device in blocking mode, a read will block (that is,
126 are two alternatives if you can't afford to wait forever (which is,
142 all events on the queue (that is, until you get a -1).
157 One reason for emptying the queue is that if it gets full you'll start
161 The other reason is that you want to know all what happened, and not
164 Why can get the queue full? Because you don't empty the queue as
170 the driver will switch to startup mode and next time you read it,
171 synthetic events (JS_EVENT_INIT) will be generated to inform you of
179 In the above code, you might as well want to read more than one event
180 at a time using the typical read(2) functionality. For that, you would
189 process the events and keep reading it until you empty the driver queue.
216 IOCTL will fail. For a compile-time decision, you can test the
226 JSIOCGNAME(len) allows you to get the name string of the joystick - the same
240 For usage on JSIOC[SG]CORR I suggest you to look into jscal.c  They are
277 As you can figure out from the example, the read returns immediately,