Lines Matching refs:events

12 Since the driver now reports events instead of polling for changes,
13 immediately after the open it will issue a series of synthetic events
51 events on open. That is, if it's issuing a INIT BUTTON event, the
56 If you choose not to differentiate between synthetic or real events
98 may work well if you handle JS_EVENT_INIT events separately,
108 have to write a separate handler for JS_EVENT_INIT events in the first
141 are no events pending to be read on the driver queue. You should read
142 all events on the queue (that is, until you get a -1).
154 		/* do something interesting with processed events */
158 missing events since the queue is finite, and older events will get
166 and too many events to store in the queue get generated. Note that
171 synthetic events (JS_EVENT_INIT) will be generated to inform you of
175  events. You can increment this size bumping up JS_BUFF_SIZE in
187 other value in which the number of events read would be i /
189 process the events and keep reading it until you empty the driver queue.