Difference between revisions of "OtfGenericScreen"
| Line 6: | Line 6: | ||
As the name said, Generic Screen is completely data driven. Only the [[ScreenSignature|Screen Signature]] have to define. Via [[OtfDataBinding|Data Binding mechanism]] the screen controls will be updated automatically and vice versa. Particular attention is paid to the [[ScreenSignature|category attributes of the parameters]]. Each category is mapped to a Pane inside the Form layout. The default layout can be used or the layout can be adapted. In most cases, the supplied default layout is sufficient. The next section shows how the layout can be changed. | As the name said, Generic Screen is completely data driven. Only the [[ScreenSignature|Screen Signature]] have to define. Via [[OtfDataBinding|Data Binding mechanism]] the screen controls will be updated automatically and vice versa. Particular attention is paid to the [[ScreenSignature|category attributes of the parameters]]. Each category is mapped to a Pane inside the Form layout. The default layout can be used or the layout can be adapted. In most cases, the supplied default layout is sufficient. The next section shows how the layout can be changed. | ||
| − | |||
In opposite to the [[OtfScreenMapping|Screen Mapping]] the layout possibilities of the Generic Screen can be adjusted in a wide range but they are limited. The layout of the Generic Screen is stored in a XML file. The file is located in: | In opposite to the [[OtfScreenMapping|Screen Mapping]] the layout possibilities of the Generic Screen can be adjusted in a wide range but they are limited. The layout of the Generic Screen is stored in a XML file. The file is located in: | ||
| Line 16: | Line 15: | ||
In the following section the generally layout is descibed. | In the following section the generally layout is descibed. | ||
| + | |||
| + | ==Screen Layout== | ||
Revision as of 12:46, 29 November 2014
Introduction
The HMI extension (Human Machine Interface) provides access for interacting with the user through the display of graphical screens. To achieve this goal, there are two ways to operate with screens:
- Basic Screen - A set of basic dialogs providing by the operating systems
- Custom Screens - Customizable screens that allow arbitrary flexibility
Custom screens only define an interface to a screen. The screen itself is externally created. The layout and functionality of this screen is not defined in the OTX. The interface to the screen is the OTX Screen Signature. A Screen Signature defines all IN-, OUT- and INOUT-Parameters of a screen. The OTX Runtime have to map the Screen Signature Parameters to the proper screen controls. The OTF supports two kinds of Custom Screens:
Generic Screen
As the name said, Generic Screen is completely data driven. Only the Screen Signature have to define. Via Data Binding mechanism the screen controls will be updated automatically and vice versa. Particular attention is paid to the category attributes of the parameters. Each category is mapped to a Pane inside the Form layout. The default layout can be used or the layout can be adapted. In most cases, the supplied default layout is sufficient. The next section shows how the layout can be changed.
In opposite to the Screen Mapping the layout possibilities of the Generic Screen can be adjusted in a wide range but they are limited. The layout of the Generic Screen is stored in a XML file. The file is located in:
ProjectFolder/HMI/ProjectName.otfSLay
Inside the folder an annotated schema file which describes the layout is also stored.
ProjectFolder/HMI/ScreenLayout.xsd
In the following section the generally layout is descibed.
