Copyright (c) 1999 - Sun Microsystems, Inc.
All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, and/or sell copies of the Software, and to permit persons
to whom the Software is furnished to do so, provided that the above
copyright notice(s) and this permission notice appear in all copies of
the Software and that both the above copyright notice(s) and this
permission notice appear in supporting documentation.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR
HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL
INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING
FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,
NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Except as contained in this notice, the name of a copyright holder
shall not be used in advertising or otherwise to promote the sale, use
or other dealings in this Software without prior written authorization
of the copyright holder.
Display * dpy\^;
unsigned int first\^;
unsigned int num\^;
XkbDescPtr xkb\^;
- dpy connection to server
- first keycode of first key to fetch
- num number of keys for which to get explicit info
- xkb Xkb description in which to put results
Whenever a client remaps the keyboard using core protocol requests, Xkb examines the map to determine likely default values for the components that cannot be specified using the core protocol (see Core Keyboard Mapping to Xkb Keyboard Mapping Transformation for more information on how Xkb chooses the default values). DO THE FOUR PAGES OF "CORE KEYBOARD MAPPING TO XKB KEYBOARD MAPPING TRANSFORMATION" NEED TO BE ADDED HERE? This automatic remapping might replace definitions explicitly requested by an application, so the Xkb keyboard description defines an explicit components mask for each key. Any aspects of the automatic remapping listed in the explicit components mask for a key are not changed by the automatic keyboard mapping. The explicit components masks are held in the explicit field of the server map, which is an array indexed by keycode. Each entry in this array is a mask that is a bitwise inclusive OR of the values shown in Table 1.
| Table 1 Explicit Component Masks |
| Bit in Explicit Mask Value Protects Against |
| ExplicitKeyType1 (1<<0) |
| Automatic determination of the key type associated with Group1. |
| ExplicitKeyType2 (1<<1) |
| Automatic determination of the key type associated with Group2. |
| ExplicitKeyType3 (1<<2) |
| Automatic determination of the key type associated with Group3. |
| ExplicitKeyType4 (1<<3) |
| Automatic determination of the key type associated with Group4. |
| ExplicitInterpret (1<<4) |
| Application of any of the fields of a symbol interpretation to the key in |
| question. |
| ExplicitAutoRepeat (1<<5) |
| Automatic determination of auto-repeat status for the key, as specified in a |
| symbol interpretation. |
| ExplicitBehavior (1<<6) |
| Automatic assignment of the XkbKB_Lock behavior to the key, if the |
| XkbSI_LockingKey flag is set in a symbol interpretation. |
| ExplicitVModMap (1<<7) |
| Automatic determination of the virtual modifier map for the key based on the |
| actions assigned to the key and the symbol interpretations that match the key. |
15 BadAlloc Unable to allocate storage
15 BadMatch A compatible version of Xkb was not available in the server or an argument has correct type and range, but is otherwise invalid
15 BadValue An argument is out of range