To meet your needs, we constantly work to improve Querix products.
This means that Lycia documentation is developing as well.
In case you have found a certain dissonance between the provided information and the actual behavior of Lycia 3 and/or your applications, please, let us know about this via documentation@querix.com so that we can introduce the necessary changes to our documentation.
Thank you for your attention and cooperation.
The Compatibility Mode property is used for the compatibility reasons, so that the developer is able to create an application which functions and behaves in a familiar way.
Depending on the user preferences a 4GL application may be run in Lycia, Informix4GL or GBDS compatibility modes. By default, Lycia compatibility mode is used. If another behavior is required, set the QX_COMPAT environment variable to the required value in the inet.env file. (e.g., QX_COMPAT=Informix4GL)
The Compatibility Mode property setting influences the appearance of an application as well as its behaviour. For example, it allows the action toolbar content and appearance manipulation. The detailed information about the features it influences and the differences in an application execution depending on the value set is given below.
|
Informix4GL |
A prompt message is displayed to the current window (by default, the PROMPT statement output is displayed to the first form line) |
|
Lycia |
A prompt message is displayed to the current window status bar (the message line) |
|
GBDS |
A prompt message is displayed to a separate dialog window |
|
Informix4GL |
A prompt message is displayed to a current window (by default, the PROMPT statement output is displayed to the first form line) |
|
Lycia |
A prompt message with a text field are displayed to a separate dialog window |
|
GBDS |
Under the action toolbar, the toolbar with the action views which are the visual representation of the actions present in an application is meant. It is created automatically at runtime and is used for triggering the action events by an application execution depending on the context.
|
Informix4GL |
The action toolbar contains the default action buttons such as accept, cancel and help, and the action views defined with the help of the toolbar group functions |
|
Lycia |
The action toolbar only contains the context actions, that cannot be invoked with the help of another window/form elements |
|
GBDS |
|
Informix4GL |
On top (horizontally) |
|
Lycia |
|
|
GBDS |
On the right (vertically) |
|
Informix4GL |
Besides the actions defined within the MENU statement, the default actions for accept, cancel and help are added to the current action list |
|
Lycia |
Only the actions explicitly defined within the MENU statement are available |
|
GBDS |
|
Informix4GL |
A regular ring menu is displayed to a current window. For correct work of ring menu in forms with GridPanel, add the LYCIA_ConvCompatGridPanel class to the GridPanel's classNames property. |
|
Lycia |
An action toolbar is used for a ring menu display |
|
GBDS |
|
Informix4GL |
The defer interrupt flag is not set |
|
Lycia |
|
|
GBDS |
An application is run as though the DEFER INTERRUPT is defined: the execution proceeds on receiving an interrupt signal during any user interaction within an application |
|
Informix4GL |
A flat window is displayed by default, unless it is specified otherwise. |
|
Lycia |
A bordered window is displayed by default |
|
GBDS |
|
Informix4GL |
A form is displayed to the current window or SCREEN |
|
Lycia |
|
|
GBDS |
Provided that an application has no open windows on the DISPLAY FORM statement execution a new bordered window to which a form is displayed is created. The size of this window corresponds to the form size (the one, defined in a form file) |
|
Informix4GL |
The first line of a form is displayed on the 3d line of a current window |
|
Lycia |
|
|
GBDS |
The first line of a form is displayed on the 1st line of a current window |
Related articles: