Eloquence A.05.00 Release Notes

Eloquence A.05.00 Release Notes


Eloquence ASCII-Windows and Dialog Manager Compatibility


Although Eloquence dialog handling and Dialog Manager are quite compatible (due to mapping performed by the driver), there are some differences.
This document describes the different behaviour between Eloquence and Dialog Manager.

Object labels


Object labels in Eloquence ASCII-Windows are not case sensitive, but they are in Dialog Manager. Dialog manager requires first character of an object label to be upper case. Eloquence will convert automatically first character in an object label to upper case.

Dialog


The Eloquence object type "dialog" is mapped to Dialog Manager "Window".
Title is displayed centered, whereas Eloquence places window title on the left upper border.
The .border attribute has no functionality except that if border is set to zero, no title bar will be displayed.
Because modal dialog windows are used to map the Eloquence dialog, you must be careful about changing the visual order of windows on the screen. Most GUI systems require closing the upper window before a lower window may be activated again.

Pushbutton


The following attributes have no functionality in Dialog Manager:
  • .adjust
  • .border
    If the object height is > 2 then object height will be reduced by 2.

    Groupbox


    Dialog Manager Groupbox object does not have a title bar.

    Listbox


    Dialog Manager Listbox object does not have a title bar. The Eloquence .multiline attribute is not supported.
    Note Be careful with the .file attribute: The corresponding file will be read from the local system. If Dialog server is running on PC platform, this file is expected on PC. This behaviour is subject to change in the next patch.


    EditText


    Dialog Manager Edittext object does not have a title bar. Attribute value will always be empty string.
    In a graphical environment (Motif, MS Windows), EditText is always in insert mode.
    Maxlines attribute is not supported. Attribute value will always be 0.
    An edittext is considered "editable" if either sensitive is true or focusable is false. An edittext is considered "sensitive" if either sensitive or focusable is true.

    EQ State AT_sensitive AT_focusable
    Sensitive & Editable true false
    Sensitive false true
    Editable false false
    (neither) false false


    There is an ambiguity in states. If a not editable not sensitive object becomes sensitive, we're in trouble. How to restore the "editable" attribute ? It will become "editable" in this implementation.

    Note Be careful with the .file attribute: The corresponding file will be read from local system. If Dialog server is running on PC platform, this file is expected on PC. This behaviour is subject to change in the next patch.


    DLG HELP


    The DLG HELP statement is not supported with Dialog Manager. This behaviour is subject to change in the next patch.
    Last update: 95/11/08