The properties contain the configurations for the user input when using the mouse or keyboard. A user input defines an event and one or more actions that are executed when an event occurs.
TIP: The “Configure” button opens the ⮫ “Dialog: Input Configuration ”, ⮫ “Introduction” dialog. There you can create or edit user inputs. Configured user inputs are listed below the events. They each include the action that is triggered and the setting in short form. Example: “Execute ST Code”: |
|
“OnDialogClosed” |
Input event: The user closes the dialog. |
“OnMouseClick” |
Input event: The user clicks the mouse button completely in the element area. The mouse button is clicked and released. |
“OnMouseDown” |
Input event: The user clicks down on the mouse button. |
“OnMouseEnter” |
Input event: The user drags the mouse pointer to the element. |
“OnMouseLeave” |
Input event: The user drags the mouse pointer away from the element. |
“OnMouseMove” |
Input event: The user moves the mouse pointer over the element area. |
“OnMouseUp” |
Input events:
NOTE: This CODESYS-specific triggering behavior guarantees that actions for key elements are completed. A key element starts an action for “OnMouseDown” and ends the action for “OnMouseUp”. Example: A visualization user presses the mouse button within the element area of the key element and then moves the cursor position so that it is located outside of the element area. The action is ended anyway because “OnMouseUp” is triggered. |
“OnValueChanged” |
Event which triggers follow-up actions due to a change in value Which follow-up actions are triggered is configured in the “Input Configuration” dialog. The defined follow-up actions and the corresponding configuration are displayed below the element property. The “OnValueChanged” event can be disabled by the “VISU_NO_VALUECHANGED” compiler define in the properties dialog of the application. |
“Tap” |
When a mouse click event occurs, the variable defined in “Variable” is described in the application. The coding depends on the “Tap FALSE” and “Tap on enter if captured” options. |
“Variable” |
Requirement: The “Tap FALSE” option is not activated. Variable (
Example: |
“Tap FALSE” |
|
“Tap on enter if captured” |
The value is |
“Switch over” |
With the onset of a mouse click event, the variable is set; when the mouse click event is completed, the variable is reset. |
“Variable” |
Variable ( This is when the user releases the mouse button while the mouse pointer is over the element area. If the user releases the mouse button while the mouse pointer is outside of the element area, then the mouse click event is not ended and the value is not toggled. TIP: The user can cancel a started toggle input by dragging the mouse pointer out of the element area. |
“Toggle on up if captured” |
|
“Hotkey” |
Shortcut on the element for triggering specific input actions When the hotkey event occurs, the input actions in the “Events” property are triggered. In this way, it is not the input action itself that leads to this input action, but the mouse input action. |
“Key” |
Key pressed for input action. Example: [T] The following properties appear when a key is selected. |
“Events” |
|
“Switch over” |
Example: [Shift]+[T]. |
“Control” |
Example: [Ctrl]+[T]. |
“Alt” |
Example: [Alt]+[T]. |
All keyboard shortcuts and their actions that are configured in the visualization are listed on the ⮫ “Command: Keyboard Configuration ” tab.