File: XGetDeviceKeyMapping.txt

package info (click to toggle)
libxi 2:1.3-8
  • links: PTS, VCS
  • area: main
  • in suites: squeeze
  • size: 2,476 kB
  • ctags: 906
  • sloc: sh: 10,500; ansic: 6,600; makefile: 454
file content (146 lines) | stat: -rw-r--r-- 5,013 bytes parent folder | download | duplicates (6)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
XGETDEVICEKEYMAPPING(libmansuffix)
==================================

NAME
----

   XGetDeviceKeyMapping, XChangeDeviceKeyMapping - query or change
   device key mappings

SYNOPSIS
--------

   #include <X11/extensions/XInput.h>

   KeySym *XGetDeviceKeyMapping( Display *display,
                                 XDevice *device,
                                 KeyCode first_keycode,
                                 int keycode_count,
                                 int *keysyms_per_keycode_return);
   display
          Specifies the connection to the X server.

   device
          Specifies the device whose key mapping is to be queried
          or modified.

   first_keycode
          Specifies the first KeyCode to be returned.

   keycode_count
          Specifies the number of KeyCodes to be returned or
          modified.

   keysyms_per_keycode
          Specifies the number of KeySyms per KeyCode.

   keysyms_per_keycode_return
          Specifies the address of a variable into which the
          number of KeySyms per KeyCodewill be returned.

   keysyms
          Specifies the address of an array of KeySyms.

DESCRIPTION
-----------

   For the specified device, the XGetDeviceKeyMapping request
   returns the symbols for the specified number of KeyCodes
   starting with first_keycode. The value specified in
   first_keycode must be greater than or equal to min_keycode as
   returned by XListInputDevices, or a BadValue error results. In
   addition, the following expression must be less than or equal
   to max_keycode as returned by XListInputDevices:

   first_keycode + keycode_count - 1

   If this is not the case, a BadValue error results. The number
   of elements in the KeySyms list is:

   keycode_count * keysyms_per_keycode_return

   KeySym number N, counting from zero, for KeyCode K has the
   following index in the list, counting from zero: (K -
   first_code) * keysyms_per_code_return + N

   The X server arbitrarily chooses the keysyms_per_keycode_return
   value to be large enough to report all requested symbols. A
   special KeySym value of NoSymbol is used to fill in unused
   elements for individual KeyCodes. To free the storage returned
   by XGetDeviceKeyMapping, use XFree.

   If the specified device does not support input class keys, a
   BadMatch error will result.

   XGetDeviceKeyMapping can generate a BadDevice, BadMatch, or
   BadValue error.

   For the specified device, the XChangeDeviceKeyMapping request
   defines the symbols for the specified number of KeyCodes
   starting with first_keycode. The symbols for KeyCodes outside
   this range remain unchanged. The number of elements in keysyms
   must be:

   num_codes * keysyms_per_keycode

   The specified first_keycode must be greater than or equal to
   min_keycode returned by XListInputDevices, or a BadValue error
   results. In addition, the following expression must be less
   than or equal to max_keycode as returned by XListInputDevices,
   or a BadValue error results:

   first_keycode + num_codes - 1

   KeySym number N, counting from zero, for KeyCode K has the
   following index in keysyms, counting from zero:

   (K - first_keycode) * keysyms_per_keycode + N

   The specified keysyms_per_keycode can be chosen arbitrarily by
   the client to be large enough to hold all desired symbols. A
   special KeySym value of NoSymbol should be used to fill in
   unused elements for individual KeyCodes. It is legal for
   NoSymbol to appear in nontrailing positions of the effective
   list for a KeyCode.XChangeDeviceKeyMapping generates a
   DeviceMappingNotify event that is sent to all clients that have
   selected that type of event.

   There is no requirement that the X server interpret this
   mapping. It is merely stored for reading and writing by
   clients.

   If the specified device does not support input class keys, a
   BadMatch error results.

   XChangeDeviceKeyMapping can generate a BadDevice, BadMatch,
   BadAlloc, or BadValue error.

DIAGNOSTICS
-----------

   BadDevice
          An invalid device was specified. The specified device
          does not exist or has not been opened by this client via
          XOpenInputDevice. This error may also occur if the
          specified device is the X keyboard or X pointer device.

   BadMatch
          This error may occur if an XGetDeviceKeyMapping or
          XChangeDeviceKeyMapping request was made specifying a
          device that has no keys.

   BadValue
          Some numeric value falls outside the range of values
          accepted by the request. Unless a specific range is
          specified for an argument, the full range defined by the
          argument's type is accepted. Any argument defined as a
          set of alternatives can generate this error.

   BadAlloc
          The server failed to allocate the requested resource or
          server memory.

SEE ALSO
--------

   XSetDeviceButtonMapping(libmansuffix), XSetDeviceModifierMapping(__libmansuffix_)