Copyright (C) 2000-2012 |
Manpages XSetDeviceButtonMappingSection: X FUNCTIONS (3X11)Updated: Release 6.5 Index Return to Main Contents NAMEXSetDeviceButtonMapping, XGetDeviceButtonMapping - query or change device button mappingsSYNTAXint XSetDeviceButtonMapping(display, device, map, nmap)Display *display; XDevice *device; unsigned char map[]; int nmap;
int XGetDeviceButtonMapping(display, device, map_return,
nmap)
ARGUMENTS
DESCRIPTIONThe XSetDeviceButtonMapping request sets the mapping of the specified device. If it succeeds, the X server generates a DeviceMappingNotify event, and XSetDeviceButtonMapping returns MappingSuccess. Element map[i] defines the logical button number for the physical button i+1. The length of the list must be the same as XGetDeviceButtonMapping would return, or a BadValue error results. A zero element disables a button, and elements are not restricted in value by the number of physical buttons. However, no two elements can have the same nonzero value, or a BadValue error results. If any of the buttons to be altered are logically in the down state, XSetDeviceButtonMapping returns MappingBusy, and the mapping is not changed.XSetDeviceButtonMapping can generate BadDevice, BadMatch, and BadValue errors. The XGetDeviceButtonMapping request returns the current mapping of the specified device. Buttons are numbered starting from one. XGetDeviceButtonMapping returns the number of physical buttons actually on the device. The nominal mapping for a device is map[i]=i+1. The nmap argument specifies the length of the array where the device mapping is returned, and only the first nmap elements are returned in map_return. XGetDeviceButtonMapping can generate BadDevice or BadMatch errors. DIAGNOSTICS
SEE ALSOXChangeDeviceKeyboardControl(3X),XChangeDeviceKeyMapping(3X) XChangeDeviceModifierMapping(3X) Programming With Xlib
IndexThis document was created by man2html, using the manual pages. Time: 18:01:54 GMT, March 28, 2024 |