Windows and Window Objects are described with statements of the form:
Widget(objektName~aliasName, Flags, x, y, w, h, statischerText, bitmap)
Widget stands for an identifier:
Window, Button, Radio, Checkbox, Menu, Item, Icon,
Group, Toolbar, Statusbar,
Prompt, String,
MultipleString, FormattedString, Text,
Integer, Numeric, Percent, Fraction, Unit,
Date, DiffuseDate,
DigitalTime, DigitalTimer,
Combobox, Enumeration, ObjectList, ObjectTree, ObjectListView,
Header, Document,
Notebook
Window objects have Parent-Child-Relations to each other - in the script, this is expressed by {}, including the child objects after the parent object (Example). Action Lists are following straight after the associated window object - even in front of a block of child objects (Example).
Window object name
Widget(objektName~aliasName, ...)
is required, if a statement is supposed to refer to this window object, whereas the window object needs to be clearly defined with a tuple which consists of the parent window name and its own name. Furthermore, a name of the form
Class::accessExpression
creates a relation between window object and objects of the so-called model classes, meaning file exchange from model to interface and vice versa are described. Access Path can be (most easily) the name of a data member, but it is also possible to navigate through the objects. If a statement refers to the window object, only the Access Path gets used as a name (sub-string after the scope operator). Another name (aliasName) can be assigned optionally, which is used in the according statements, as well as the object name. For long access paths, this allows for a more comfortable syntax, and it is possible to resolve ambiguity with the alias name (e.g. if two instances of the same class are displayed in the window).