2
2
.\" Title: xiquerydevice
3
3
.\" Author: [FIXME: author] [see http://docbook.sf.net/el/author]
4
4
.\" Generator: DocBook XSL Stylesheets v1.76.1 <http://docbook.sf.net/>
6
6
.\" Manual: [FIXME: manual]
7
7
.\" Source: [FIXME: source]
8
8
.\" Language: English
10
.TH "XIQUERYDEVICE" "libmansuffix" "06/02/2011" "[FIXME: source]" "[FIXME: manual]"
10
.TH "XIQUERYDEVICE" "libmansuffix" "12/22/2011" "[FIXME: source]" "[FIXME: manual]"
11
11
.\" -----------------------------------------------------------------
12
12
.\" * Define some portability stuff
13
13
.\" -----------------------------------------------------------------
218
218
The type field specifies the type of the input class\&.
219
219
Currently, the following types are defined:
220
XIKeyClass, XIButtonClass, XIValuatorClass
220
XIKeyClass, XIButtonClass, XIValuatorClass, XIScrollClass,
493
This class describes scrolling capability on a valuator\&. For
494
each XIScrollClassInfo, an XIValuatorClassInfo with the same
495
number is present on the device\&.
505
The number field specifies the valuator number on the physical
506
device that this scroll information applies to\&. See the
507
respective XIValuatorClassInfo for detailed information on this
518
The scroll_type field specifies the type of scrolling, either
519
XIScrollTypeVertical or XIScrollTypeHorizontal\&.
529
The increment specifies the value change considered one unit of
540
The flags field specifies flags that apply to this scrolling
551
If XIScrollFlagNoEmulation is set, the server will not
552
emulate legacy button events for valuator changes on this
563
If XIScrollFlagPreferred is set, this axis is the
564
preferred axis for this scroll type and will be used for
565
the emulation of XI_Motion events when the driver submits
566
legacy scroll button events\&.
592
A device may have zero or one XITouchClassInfo, denoting
593
multi\-touch capability on the device\&. A device with a XITouchClassInfo
594
may send TouchBegin, TouchUpdate, TouchEnd and TouchOwnership events\&.
604
The mode field is either XIDirectTouch for direct\-input touch devices
605
such as touchscreens or XIDependentTouch for indirect input devices such
606
as touchpads\&. For XIDirectTouch devices, touch events are sent to window
607
at the position the touch occured\&. For XIDependentTouch devices, touch
608
events are sent to the window at the position of the device\*(Aqs sprite\&.
618
The num_touches field defines the maximum number of simultaneous touches
619
the device supports\&. A num_touches of 0 means the maximum number of
620
simultaneous touches is undefined or unspecified\&. This field should be
621
used as a guide only, devices will lie about their capabilities\&.
631
A device with an XITouchClassInfo may still send pointer events\&. The
632
valuators must be defined with the respective XIValuatorClass
633
classes\&. A valuator may send both pointer and touch\-events\&.
474
643
XIQueryDevice can generate a BadDevice error\&.