NAME

VirtualBindings — Bindings for virtual mouse and key events.

DESCRIPTION

The OSF/Motif manual pages describe translations in terms of virtual bindings, based on those described in the OSF/Motif Style Guide.  Mouse events are described in terms of virtual buttons, and key events are described in terms of virtual keys.  The term virtual implies that the events as described do not necessarily correspond to a fixed set of X Window System events.  Instead, virtual buttons and keys are linked to actual events by means of virtual bindings. 

Virtual Modifiers

Both virtual buttons and virtual keys may contain virtual modifiers.  Each virtual modifier corresponds to one or more actual modifiers.  The following table lists the bindings of virtual modifiers to actual modifiers in OSF/Motif:

Mod1 refers to the first modifier key.  OSF/Motif requires that it correspond to either Alt or Meta. 

The virtual modifier MAny indicates that any modifier can be used.  If MAny is not specified and the user presses an actual modifier that is not explicitly included in a translation, that modifier may prevent the translation from being matched. 

Virtual Buttons

Each virtual button corresponds to one or more actual button event descriptions.  Each button event description contains a button name and possibly modifiers.  These button event descriptions, appropriately ordered and possibly further modified, are used in translation tables.  The following table lists the bindings of virtual buttons to actual button event descriptions in OSF/Motif:

Virtual Keys

Each virtual key corresponds to one or more actual key event descriptions.  Each key event description contains a keysym name and possibly modifiers.  These key event descriptions, appropriately ordered and possibly further modified, are used in translation tables.  The following table lists the bindings of virtual keys to actual key event descriptions in OSF/Motif:

Bindings for osf Keysyms

Keysym strings that begin with "osf" are not part of the X server’s keyboard mapping.  Instead, these keysyms are produced on the client side at run time and are used by the translation manager when the server delivers an actual key event.  A mapping is maintained between "osf" keysyms and actual keysyms.  This mapping is based on information obtained from one of the following sources, listed in order of precedence:

•A _MOTIF_BINDINGS property on the root window of screen 0.  The Motif Window Manager sets this property when it starts up, taking the contents from the .motifbind file in the user’s home directory. 

•An XmNdefaultVirtualBindings application resource in the resource database. 

•A fixed default based on the vendor string returned by the X server during the call to XOpenDisplay. 

•A fixed fallback default. 

The format of the specification for mapping "osf" keysyms to actual keysyms is similar to that of a specification for an event translation.  The syntax is specified here in EBNF notation using the following conventions:

[a]Means either nothing or a
{a}Means zero or more occurrences of a

Terminals are enclosed in double quotation marks. 

The syntax of an "osf" keysym binding specification is as follows:

binding_spec={line "\n"} [line]
line=virtual_keysym ":" key_event
key_event={modifier_name} "<Key>" actual_keysym
virtual_keysym=keysym
actual_keysym=keysym
keysym=A valid X11 keysym name that is
mapped by XStringToKeysym

As with event translations, more specific event descriptions must precede less specific descriptions.  For example, an event description for a key with a modifier must precede a description for the same key without the same modifier. 

Following is an example of a specification for the XmNdefaultVirtualBindings resource in a resource file:

∗defaultVirtualBindings: \
osfBackSpace:<Key>BackSpace \n\
osfInsert:<Key>InsertChar \n\
osfDelete:<Key>DeleteChar

The format of a .motifbind file is the same, except that the binding specification for each keysym is placed on a separate line.  The example specification above appears as follows in a .motifbind file:

osfBackSpace:<Key>BackSpace
osfInsert:<Key>InsertChar
osfDelete:<Key>DeleteChar

The following table lists the fixed fallback default bindings for "osf" keysyms:

Sun Release 4.0  —  Last change: