Difference between revisions of "OtfScreenMapping"
| Line 4: | Line 4: | ||
==Screen Mapping== | ==Screen Mapping== | ||
| − | In opposite to the [[OtfGenericScreen|Generic Screen]], which is completely generic, easy to use but limited, the Screen Mapping is not limited related to the layout or the used controls. | + | In principal the Screen Mapping bounds the properties of controls found in a form of an .NET assembly (*.dll or *.exe) to OTX [[ScreenSignature|Screen Signature Parameters]] via [[OtfDataBinding|Data Binding]]. In opposite to the [[OtfGenericScreen|Generic Screen]], which is completely generic, easy to use but limited, the Screen Mapping is not limited related to the layout or the used controls. |
| + | |||
| + | ===Windows Forms=== | ||
| + | For the Screen Mapping the user have to create an executable application (*.exe) or an assembly (*.dll) with one or more [http://msdn.microsoft.com/en-us/library/8bxxy49h(v=vs.110).aspx Windows Forms]. This job can be done graphically with the [http://msdn.microsoft.com/en-us/library/e06hs424%28v=vs.110%29.aspx Windows Forms Designer] of [http://www.visualstudio.com/ Microsoft Visual Studio] or with free [http://www.icsharpcode.net/opensource/sd/tour/090/formsdesigner.asp Forms Designer] of [http://www.icsharpcode.net SharpDevelop]. All [http://msdn.microsoft.com/en-us/library/ettb6e2a(v=vs.110).aspx controls] found in that form can be bound to [[ScreenSignature|Screen Signature Parameters]] via the Screen Mapping Editor, see below. The form can contain arbitrary program logic or can be just a form with controls and without internal logic. | ||
| + | |||
| + | ===Screen Mapping Editor=== | ||
| + | |||
| + | ===Data Bound Component=== | ||
Revision as of 20:22, 29 November 2014
Contents
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:
Screen Mapping
In principal the Screen Mapping bounds the properties of controls found in a form of an .NET assembly (*.dll or *.exe) to OTX Screen Signature Parameters via Data Binding. In opposite to the Generic Screen, which is completely generic, easy to use but limited, the Screen Mapping is not limited related to the layout or the used controls.
Windows Forms
For the Screen Mapping the user have to create an executable application (*.exe) or an assembly (*.dll) with one or more Windows Forms. This job can be done graphically with the Windows Forms Designer of Microsoft Visual Studio or with free Forms Designer of SharpDevelop. All controls found in that form can be bound to Screen Signature Parameters via the Screen Mapping Editor, see below. The form can contain arbitrary program logic or can be just a form with controls and without internal logic.
