Migrated GUI Screens

While the ideal migration includes safe passage of all your application’s GUI screens, it is a good idea to ensure GUI elements have been migrated successfully before building the application. For example, line styles Dash-Dot and Dash-Dot-Dot are migrated as Dash and Outset respectively, and the Underbar attribute is migrated as Borderstyle = FixedSingle. You might also want to make minor adjustments to the screens before building. However, AB Suite imports both, Dash-Dot, and Dash-Dot-Dot as Dashes.

In System Modeler, any named element can have a form created for it when its PresentationType property is set to a value other than None, with the exception of the model, a business segment, a report or a folder. For any migrated element with existing presentation elements, the PresentationType property is automatically set to Graphical and Fixed.

Some properties that existed in screens created in EAE 3.3 no longer make sense in the graphical environment of System Modeler. For example, some Keyword properties such as Blink and Reset are not relevant for GUI screens and are therefore ignored by System Modeler during migration. The controls these properties are associated with continue to act as they did in EAE 3.3, but the irrelevant properties are lost.

When migrating an EAE mdl file to AB Suite, the Import process needs to calculate the size of graphical display items (labels) in pixels (height and width). This is done by making a call to the operating system to calculate the size for a display item, given the text and the font. In order for this to be done correctly, and to give a valid size in pixels, the following conditions must be satisfied on the machine upon which the import is run:

Note: When making a change on a Fixed painter after migration, the values of the Bold and Text properties change when the Bright property is set to True. For example, consider two models having different versions of an element of Fixed screen presentation.

  • A: The model exported after migrating the element to AB Suite.

  • B: The model exported after making an unrelated change on the Fixed painter.

If you compare the model files A and B using the Compare.exe utility, the comparison for a control with the Bright property set to True changes the value of the Bold property from "Yes" to BLANK, and the value of the Text property from BLANK to "^". These changes do not make any difference to the presentation in developer or at runtime for MCP. You can proceed with accepting them.