Now that you have added the generated assembly for your screen definition file, you have access to a number of class members based on the names of your screens, screenmaps and fields.
| Enumerations | Keep track of all the "hooks" into your screen-based application |
| Classes and Structures | For each FieldMap a unique class or structure |
| Methods | Read and Write field maps and manage fields |
| Properties | Some indexed arrays and other useful properties |
Enumerations
You also have a number of enumerations defined which help avoid the need for memorizing or referring to outside lists of screens, maps and so on. These include:
ScreenID |
One for each screen, integer based |
MapID |
One for each screenmap, integer based |
FieldID |
One for each field. Mapper ensures that fields of the same name have the same length definition, so if a field has the same name but a different length than the first definition of that field, it will have the mapname, an underscore and the field name in the FieldID enumeration |
The enumerations are namespace scoped, so you have simple access to them using the enumeration name. For example, the HostScreen.getScreenID() method will return an integer that you can cast to a ScreenID, as follows:
