diff options
| author | marha <marha@users.sourceforge.net> | 2010-07-13 07:35:01 +0000 |
|---|---|---|
| committer | marha <marha@users.sourceforge.net> | 2010-07-13 07:35:01 +0000 |
| commit | 81124070f120ab658e094b64f6944d701b003a99 (patch) | |
| tree | 735e49473d8c4545e39cf98981e3dcdfd70760f9 /xorg-server/xkbdata.src/compat/README | |
| parent | f2388fcb82e72ee921139e9a4c8f9223e4ae04cd (diff) | |
| download | vcxsrv-81124070f120ab658e094b64f6944d701b003a99.tar.gz vcxsrv-81124070f120ab658e094b64f6944d701b003a99.tar.bz2 vcxsrv-81124070f120ab658e094b64f6944d701b003a99.zip | |
Renamed xkbdata.src to xkeyboard-config (to reflect the name in the git repository)
Diffstat (limited to 'xorg-server/xkbdata.src/compat/README')
| -rw-r--r-- | xorg-server/xkbdata.src/compat/README | 33 |
1 files changed, 0 insertions, 33 deletions
diff --git a/xorg-server/xkbdata.src/compat/README b/xorg-server/xkbdata.src/compat/README deleted file mode 100644 index 00d591e7b..000000000 --- a/xorg-server/xkbdata.src/compat/README +++ /dev/null @@ -1,33 +0,0 @@ -The core protocol interpretation of keyboard modifiers does not include direct -support for multiple keyboard groups, so XKB reports the effective keyboard -group to XKB-aware clients using some of reserved bits in the state field of -some core protocol events. This modified state field would not be interpreted -correctly by XKB-unaware clients, so XKB provides a group compatibility mapping -which remaps the keyboard group into a core modifier mask that has similar -effects, when possible. - -XKB maintains three compatibility state components that are used to make -XKB-unaware clients(*) work as well as possible: -- The compatibility state which corresponds to the effective modifier and - effective group state. -- The compatibility lookup state which is the core-protocol equivalent of the - lookup state. -- The compatibility grab state which is the nearest core-protocol equivalent - of the grab state. - -Compatibility state are essentially the corresponding XKB states, but with -keyboard group possibly encoded as one or more modifiers. - -Modifiers that correspond to each keyboard group are described in this -group compatibility map. - - ----- -(*) The implementation of XKB invisibly extends the X library to use the -keyboard extension if it is present. That means, clients that use library or -toolkit routines to interpret keyboard events automatically use all of XKB -features; clients that directly interpret the state field of core protocol -events or the keymap direcly may be affected by some of the XKB differences. -Thus most clients can take all advantages without modification but it also -means that XKB state can be reported to clients that have not explicitly -requested the keyboard extension. |
