101
101
The type field specifies the type of the input class.
102
102
Currently, the following types are defined:
103
XIKeyClass, XIButtonClass, XIValuatorClass
103
XIKeyClass, XIButtonClass, XIValuatorClass, XIScrollClass,
105
106
In the future, additional types may be added. Clients are
106
107
required to ignore unknown input classes.
194
195
XIModeAbsolute this axis sends absolute coordinates. If the
195
196
mode is XIModeRelative, this device sends relative coordinates.
208
This class describes scrolling capability on a valuator. For
209
each XIScrollClassInfo, an XIValuatorClassInfo with the same
210
number is present on the device.
212
The number field specifies the valuator number on the physical
213
device that this scroll information applies to. See the
214
respective XIValuatorClassInfo for detailed information on this
217
The scroll_type field specifies the type of scrolling, either
218
XIScrollTypeVertical or XIScrollTypeHorizontal.
220
The increment specifies the value change considered one unit of
223
The flags field specifies flags that apply to this scrolling
226
If XIScrollFlagNoEmulation is set, the server will not
227
emulate legacy button events for valuator changes on this
230
If XIScrollFlagPreferred is set, this axis is the
231
preferred axis for this scroll type and will be used for
232
the emulation of XI_Motion events when the driver submits
233
legacy scroll button events.
243
A device may have zero or one XITouchClassInfo, denoting
244
multi-touch capability on the device. A device with a XITouchClassInfo
245
may send TouchBegin, TouchUpdate, TouchEnd and TouchOwnership events.
247
The mode field is either XIDirectTouch for direct-input touch devices
248
such as touchscreens or XIDependentTouch for indirect input devices such
249
as touchpads. For XIDirectTouch devices, touch events are sent to window
250
at the position the touch occured. For XIDependentTouch devices, touch
251
events are sent to the window at the position of the device's sprite.
253
The num_touches field defines the maximum number of simultaneous touches
254
the device supports. A num_touches of 0 means the maximum number of
255
simultaneous touches is undefined or unspecified. This field should be
256
used as a guide only, devices will lie about their capabilities.
258
A device with an XITouchClassInfo may still send pointer events. The
259
valuators must be defined with the respective XIValuatorClass
260
classes. A valuator may send both pointer and touch-events.
197
262
XIQueryDevice can generate a BadDevice error.
199
264
XIFreeDeviceInfo frees the information returned by