klein@lupine.UUCP (Doug Klein ) (09/28/88)
The 'state' field in the XKeyEvent structure has pre-defined fields for SHIFT, CONTROL, and LOCK, with 5 extra fields for server dependant masks, Mod[1-5]. The convention for META is currently Mod1, (is this enforced anywhere?), but I haven't noticed any applications assuming any other conventions. Is there any general consensus on defining any other "standard" uses of the Mod's? For instance, has anyone seen any applications looking for the NUMLOCK modifier, as in a PC style keyboard? -- Doug Klein Network Computing Devices uunet!lupine!klein
swick@ATHENA.MIT.EDU (Ralph R. Swick) (09/28/88)
Date: 27 Sep 88 19:19:56 GMT
From: lupine!klein@uunet.uu.net (Doug Klein )
The convention for META is currently Mod1,
only by weight of existing client documentation.
(is this enforced anywhere?),
no. The Protocol is very explicit about there being only three
modifier keys with standard names. Clients who refer to "Meta"
in their documentation when they really mean "Mod1" are in error.
The appropriate definition of the Meta modifier is
"that modifier whose corresponding keysym mapping
contains either Meta_L or Meta_R."
That is, you need to perform a search of both the modifier mapping
table and the keyboard mapping table to determine where the user
has placed the Meta key.
The R3 Xt supports this automagically through the translation
manager. (need I have said that? :-)