OtfAssemblyScreenMapping

From emotive
Jump to navigation Jump to search

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:

  1. Basic Screen - A set of basic dialogs providing by the operating systems
  2. 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:

  1. Generic Screen
  2. Screen Mapping

Screen Mapping

In principal the Assembly Screen Mapping bounds properties and methods found in a special class which is marked with certain attributes from of an .Net Assembly (*.dll) 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.

To apply the screen mapping, the following steps have to be performed:

  1. Create an .Net Assembly
  2. Create a Screen Mapping file via the Screen Mapping Editor
  3. Select the Screen Mapping file in the runtime settings of the project

...