Content
A content is an independent container object that can be loaded in a region. A content can be used, for example, to subdivide operating concepts into various contents. It is created under the TcHmi project tree with the context menu Add new Item…
Attributes
Category: Colors
Name |
Description |
---|---|
Definition of the background color | |
Definition of the border color of the control |
Category: Layout
Name |
Description |
---|---|
Definition of the distance from the left side to the left side of the surrounding control | |
Definition of the unit of the distance to the right side of the surrounding control:
| |
Definition of the distance from the top side to the top side of the surrounding control | |
Selection of the unit of the distance to the top side of the surrounding control:
| |
Definition of the distance from the right side to the right side of the surrounding control | |
Selection of the unit of the distance to the right side of the surrounding control:
| |
Definition of the distance from the bottom side to the bottom side of the surrounding control | |
Selection of the unit of the distance to the bottom side of the surrounding control:
| |
Definition of the external width of the control | |
Selection of the unit of the width:
| |
Definition of the external height of the control | |
Selection of the unit of the height:
| |
Definition of the maximum width if the control size is defined as dynamic. | |
Selection of the unit of the maximum width:
| |
Definition of the minimum width if the control size is defined as dynamic. | |
Selection of the unit of the minimum width:
| |
Definition of the maximum height if the control size is defined as dynamic. | |
Selection of the unit of the maximum height:
| |
Definition of the minimum height if the control size is defined as dynamic. | |
Selection of the unit of the minimum height:
| |
Calculated distance in pixels from the left side to the left side of the surrounding control | |
Calculated distance in pixels from the top side to the top side of the surrounding control | |
Calculated distance in pixels from the right side to the right side of the surrounding control | |
Calculated distance in pixels from the bottom side to the bottom side of the surrounding control | |
Calculated width of the control in pixels | |
Calculated height of the control in pixels | |
Definition of the row of a grid in which the control is to be displayed. | |
Definition of the column of a grid in which the control is to be displayed. | |
Definition of the transparency of the entire control | |
Selection of the visibility of a control:
| |
Definition of the position on the Z-axis | |
Definition of a transformation of a control:
| |
Definition of a shadow | |
Selection of the method of calculating the width:
| |
Selection of the method of calculating the height:
|
Category: Common
Name |
Description |
---|---|
Selection of whether the control is enabled. | |
Definition of the name of the control | |
Type name of the control | |
Definition of control classes | |
If a control is logically assigned in the DOM. | |
Definition of the tooltip for the control |
Category: Border
Definition of the radius of the four corners to round them off | |
Selection of the border style of the four sides of the control | |
Definition of the border width of the four sides of the control |
Category: Background Image
Name |
Description |
---|---|
Definition of an image that is located above the background color | |
Definition of the height of the background image | |
Selection of the unit of the height of the background image:
| |
Definition of the width of the background image | |
Selection of the unit of the width of the background image:
| |
Definition of an additional distance between the border of the control and background image for the four sides | |
Definition of the vertical alignment of the background image within the control | |
Definition of the horizontal alignment of the background image within the control |
Events
Category: Framework
Name |
Description |
---|---|
The control was added to the display. | |
The control was removed from the display. | |
The control was initialized. | |
The control was destroyed. | |
The control was moved in relation to the browser window. | |
The size of the control was changed. |
Category: Operator
Name |
Description |
---|---|
A mouse click was executed or a touch screen was briefly touched. | |
The left mouse button was clicked over the control and released. | |
The left mouse button was clicked twice over the control and released. | |
The right mouse button was clicked over the control and released. | |
A mouse button was pressed down over the control. | |
The mouse pointer was moved over the control. | |
The mouse pointer has left the control. | |
A mouse button was released over the control. | |
The left mouse button was pressed down over the control. | |
The right mouse button was pressed down over the control. | |
The mouse was moved over the control. | |
The mouse pointer was moved over the control or one of its children. | |
The mouse pointer has left the control or one of its child controls. | |
The left mouse button was released over the control. | |
The right mouse button was released over the control. | |
The mouse wheel was moved over the control. | |
A finger/stylus was placed against a touch screen. | |
A finger/stylus was moved on a touch screen. | |
A finger/stylus was lifted off a touch screen. | |
An interaction with a touch screen was aborted. |
Access rights
Name |
Description |
---|---|
Determines whether the control is generally observable. | |
Determines whether the control is generally operable. |
Behavior in the life cycle
A view control can behave differently during its life cycle. If you select the view file in the project tree, you can select the following settings:
Preload: Defines whether the file should be loaded and compiled during initialization to speed up later use. The default value False
increases the speed of the initial loading process of the HMI, but can lead to a reduction in the loading speed of individual HMI pages on which many controls are instantiated. Memory consumption is also reduced because the pages are no longer in memory when they are not active.
KeepAlive: Defines whether the compilation result should be saved temporarily after the first use in order to speed up subsequent use. The default value is False.
If this option is enabled, the controls are kept in the browser cache. This increases the loading speed of a single HMI page if it is called several times. The controls of a page are created when the page is accessed for the first time. They are retained when the page is exited. This only slightly increases memory consumption, since only those pages remain in memory that were enabled once.
Pages with KeepAlive are therefore kept in memory similar to Preload when they are no longer needed. In contrast, these pages are not loaded initially. This ensures fast loading of the entire application.
LoadSync: Defines whether the content should be loaded synchronously. The default value is False
.
PreloadBindings: Defines whether bindings to controls in this file should be preloaded before the content is displayed in order to have correct values when displaying the content. Requires that Preload is enabled. The default value is False
.
Please also note the background information on the life cycle for control development.
Inheritance hierarchy
Content
NuGet package: Beckhoff.TwinCAT.HMI.Framework
![]() | NuGet packages are available from version 1.12. |
![]() | Available from version 1.10 |
See also
API reference for this control