GUIBlock Element/en: Unterschied zwischen den Versionen
Cg (Diskussion | Beiträge) |
Cg (Diskussion | Beiträge) |
||
| Zeile 12: | Zeile 12: | ||
When closed via Accept", they generate updated values at corresponding output pins. |
When closed via Accept", they generate updated values at corresponding output pins. |
||
Read more in [[GUI_Editor-GUICode_Editor/en#Example:_A_Modal_Forms_Dialog]] |
Read more in the chapter [[GUI_Editor-GUICode_Editor/en#Example:_A_Modal_Forms_Dialog | "A Modal Forms Dialog" ]] of the GUI Editor documentation. |
||
=== Compound GUI actions === |
=== Compound GUI actions === |
||
Version vom 12. August 2019, 20:18 Uhr
A GUI block is used to model user interfaces such as a form's dialog box or a file viewer, browser or a graphic display view. It can be created or modified in the UI editor.
Two variants are provided:
- Simple Elementary GUI actions
- Compound GUI actions
Inhaltsverzeichnis
Simple Elementary GUI actions[Bearbeiten]
These are easy to define, but offer no workflow, other than displaying incoming values and producing output values. They can be used to generate custom data entry dialogs, simple file viewers, etc.
When opened, they will render their input values in corresponding GUI widgets, such as labels, lists, tables, etc. When closed via Accept", they generate updated values at corresponding output pins.
Read more in the chapter "A Modal Forms Dialog" of the GUI Editor documentation.
Compound GUI actions[Bearbeiten]
These are more complicated, in that they need an underlying activity diagram, which controls the operation of the user interface. However, almost any UI interaction can be implemented this way.
Compound GUI actions[Bearbeiten]
See Also[Bearbeiten]
A detailed example on how to define and use GUI blocks is found in the "A Modal Forms Dialog".
