VADELIA and MADELIA type programs manipulate graphical objects.
This chapter presents all the basic graphical objects (BGO) included with the Visual Adelia package.
- Properties
- Associated Constants
- Events
- Methods
- Restrictions with Programs Generated in Cloud
- Restrictions with Programs Generated in Java
- Restrictions with programs Generated in Mobile
- Alphabetical List of the Visual Adelia Basic Graphical Objects
For each BGO, the following elements are detailed:
the properties,
the associated constants,
the events,
the methods.
A graphical object is characterized by a set of properties.
You can create personalized graphical objects from basic graphical objects, by modifying their properties. Therefore you can build up a catalog of personalized graphical objects to suit the specific activities of your company.
A personalized graphical object can also contain code making it possible to specify its behavior.
Using a personalized graphical object lets you avoid repeating input of the source for objects with the same behavior. When associated with the new keywords %OBJECT and %WINDOW, it is possible to write generic code for an object.
A personalized graphical object can declare its own variables and procedures, and provide standard behavior for event processing blocks.
The code associated with the PGO is automatically inserted in the code of the programs or windows in which the PGO is used. Tools are provided to reproduce, manually or automatically, the changes to the source of a PGO in the code of the programs using it.
Specifics and/or limitations relating to the following points should be taken into account:
Variables declared by a PGO
PGO variable declarations are inserted in the declaration block of the window in which the PGO is used. Although double (identical) declaration is authorized here, remember that all the PGOs of a window using a variable X share a single instance of this variable.
Moreover, if two different PGOs define this variable, they can only be used in the same window if the definition (type, length, etc.) of the variable is strictly identical for both objects.
Procedures from a PGO
Procedures from a PGO are inserted in the program with a name qualified by the static name of the PGO.
It is possible to use a procedure from a PGO in the program body, by using the qualified name of the procedure in the PROCESS_PROC call.
It is not necessary (or recommended) to qualify the name of the procedure in the PGO source body. In the PGO source, verification of the PROCESS_PROC instruction first looks for a local procedure to the PGO before searching for a procedure from the program.
It is therefore possible to have a procedure with the same name at the program level and PGO level.
Specifics relating to reproduction of changes - BEGIN_PGO and END_PGO instructions
The code associated with a PGO is inserted in the program's source blocks between the BEGIN_PGO and END_PGO instructions. When changes are reproduced, these instructions are fully rewritten.
If the object code is specified at program level, this should be carried out outside the BEGIN_PGO/END_PGO instructions; if not, the changes will be lost during reproduction.
Changes are reproduced according to the following algorithm:
the blocks present in the PGO source and absent from the program are created.
the blocks present in the program source and absent from the PGO source are left intact.
the blocks present in both sources are updated as follows:
- if the program block contains the BEGIN_PGO/END_PGO instructions, the code between these two instructions is replaced by the code of the corresponding block in the PGO.
- if the program block does not contain the BEGIN_PGO/END_PGO instructions, the block source is not modified.
Click below for further details about: