Mapping mouse triggers for the Desktop
The actions that are taken in response to a mouse action
(clicking, dragging, or holding one or more mouse
buttons) are defined by associating them with a trigger name
instead of a specific physical mouse button.
For example, the action ``select an icon'' is
associated with the trigger name ``activate'' instead of
being directly defined as the mouse action
``double-click mouse button 1.''
This mapping of mouse actions with trigger names
allows you to define action sequences for any type of
mouse containing one to five mouse buttons.
Although the SCO OpenServer system
offers this flexibility in mapping triggers,
you are advised against modifying this mapping indiscriminately.
The trigger mapping is optimized to the particular
mouse supplied with your system.
Make changes with caution because any change you make
has possible effects on other trigger functionality.
Furthermore, the mouse trigger mappings are currently defined
so that they are OSF/Motif compliant for three-button mice.
Altering these trigger mappings will alter this compliance.
There are three resources
that define mouse actions for the Desktop:
These resources control the time (milliseconds) that a mouse button
can be up before a trigger ends (used to judge
whether two button presses are a double-click or two independent clicks),
the time (milliseconds) that a mouse button
can be held before it is considered a hold instead of a click,
and the distance (pixels) that the mouse pointer can move
before a mouse button press is considered a drag, respectively.
For more information on these resources, see
``Configuring mouse behavior''.
Modifying the mouse trigger mappings
© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003