genre | Interaction |
author | Uwe Siems |
package | MeVisLab/Standard |
dll | SoInteractionControllers |
definition | SoInteractionControllers.def |
keywords | entries, event, managed, scheme |
This module list interactions provided through the new managed interaction scheme.
Connect the Open Inventor (sub-)scene containing interactions to the module input. Trigger Update to update the information. The information will be listed in different tabs.
Actions (availablePointingActions): String | Icon file: String |
Actions (availableCommandActions): String | ID: String |
Actions (availableOffsetActions): String | Is enabled: Bool |
Description: String | Sub-type: String |
Detailed (pointingActions): String | Triggers: String |
Detailed (commandActions): String | Type: Enum |
Detailed (offsetActions): String | Update: Trigger |
Exists: Bool | User name: String |
Trigger this to update the information about the connect (sub-)scene.
Shows the names of all available pointing (mouse pointer) actions in the (sub-)scene.
Shows the names of all available command (keyboard) actions in the (sub-)scene.
Shows the names of all available offset (e.g. mouse wheel) actions in the (sub-)scene.
This field lists the available pointing actions with more details. Each action is listed in a separate line. For each action it's full (internal) name, icon file, trigger and user name are listed, separated by @. The trigger is the mouse button and modifier combo that activate that action by default. The mouse buttons are indicated by the numbers 1-3 where 1 is the left mouse button, 2 the right and 3 the middle (is this correct?). Modifiers are indicated by letters S (Shift), C (Control) and A (Alt). If modifiers or mouse buttons are followed by a "?", they are completely ignored when checking if the action should be triggered.
This field lists the available command actions with more details. Each action is listed in a separate line. For each action it's full (internal) name, icon file, trigger and user name are listed, separated by @. The trigger is the key combo that activates that action by default. This is some key name, prepended with "Shift-", "Ctrl-" and "Alt-" for keyboard modifiers.
This field lists the available offset actions with more details. Each action is listed in a separate line. For each action it's full (internal) name, icon file, trigger and user name are listed, separated by @. The trigger can have different types, since offset actions may be mapped to different input devices.
If mapped to a mouse wheel, the trigger starts with "wheel:" and some key modifiers as specified for Detailed or Detailed.
If mapped to mouse movement, the trigger starts with "button:" and a trigger specifier as described for Detailed.
If mapped to key presses, the trigger starts with "key:" and one or two shortcut specifiers as described for Detailed. If there are two shortcuts (for opposite directions) they are separated by a slash ("/").
In each case this may be followed by one or two numeric sensitivity values, and the keyword "swap" if horizontal and vertical offset values should be swapped. These are separated by a ";".
Set this to an action type (POINTING_ACTION or COMMAND_ACTION or OFFSET_ACTION) to get detailed, broken-down information about an action. This must be used together with ID.
Values:
Title | Name |
---|---|
Pointing Action | POINTING_ACTION |
Command Action | COMMAND_ACTION |
Offset Action | OFFSET_ACTION |
This field shows the trigger for the action selected with ID and Type (remember to update the information with Update). A trigger must not necessarily be set for an action. See documentation for Detailed, Detailed, and Detailed for a description of the format of this string.