Containers
When you create a form is empty and you have to put a container in it. This first container is called the root container.
Inside of the root container you can place the containers and widgets that you need.
The choice of the root container influences
- form behavior at runtime,
- form resizing possibitilies, and
- layout specialties.
In BorderPanel, elements are placed alongside the panel borders or in its center. BorderPanel can incorporate up to 5 elements. When placed in BorderPanel, an element takes all available space along the selected border. The position of an element inside a BorderPanel is defined in the borderPanelItemLocation property.
Container-specific properties: borderPanelItemLocation
CoordPanel is the most commonly used container for legacy compatible forms since it fully supports the legacy DISPLAY...AT statement. Any element placed within CoordPanel will be positioned in classic 4GL rows and columns.
Container-specific properties: location
GridPanel places elements in grid cells. Each element must occupy at least one grid cell. Two elements cannot occupy the same grid cell.
Grid lines are only visible during panel manipulations in Lycia Form Designer, and are not visible at runtime. You can define the number of rows, columns, and their size.
Container-specific properties: GridLengthValue, GridMaxLength, GridMinLength, gridItemLocation (for child elements)
GroupBox stores only one element (a widget or any container with its own children) inside a visible border with an optional titled frame at the top. Although GroupBox can have a widget as a child element, typically it includes a container first.
Container-specific properties:title, titleJustification
StackPanel arranges elements in horizontal or vertical stacks. Elements are automatically aligned and placed under each other or next to each other, depending on the panel orientation. At runtime, the contents of the stack panel can be resized only in the direction opposite to the orientation of the container.
Container-specific properties: orientation
Tab container is used for storing only TabPage containers. Tab container does not create any TabPages, but allocates space for them.
Container-specific properties: TabPagePlacement
TabPage is a container that can only be placed inside the Tab container. A TabPage can contain one element (widget or container with its child elements). Each tab page has a title which is used to bring it to front at runtime or during form modification.
Container-specific properties: image, title
ScrollViewer container allows to store content with dimensions larger than ScrollViewer itself. Horizontal and vertical scroll bars allow to view the hidden content. ScrollViewer can store only one child.
Table allows to create tables for data input and display. A form table has a hierarchical structure, in which the Table is the main parent object. Each widget placed inside the Table appears under a separate table column in the Structure view.
Container-specific properties: IsMultiselect, RowCount, RowHeight, unsortableColumn
TreeTable allows to create tree tables without having to specify additional theme properties and settings.
A TreeTable has all the properties the standard table has and acquires some specific ones. TreeTable includes
- columns that are displayed,
- columns that regulate the parent-child relations between the nodes, and
- columns which specify additional settings.
Container-specific properties: ColumnEdit, ColumnID, ColumnIsNode , ColumnParentId, ColumnExpanded, ColumnImage
Related articles