HP Eloquence A.06.31 Release Notes

A.06.31 Release Notes

Windows GUI components

This document covers fixes and enhancements which have been integrated into the HP Eloquence A.06.31 GUI components on the Windows platform.

Contents of this document:

DLG Server
- New functionality
- Fixed problems
RUN Server

DLG Server

The following changes have been included with the 16 and 32-bit dlgsrv on the Windows platform.

New functionality

The on-line help browser now can be configured in the [DlgSrv] section of your HP Eloquence client configuration file:

  HelpDDEModule=netscape

For the 32bit dlgsrv32, this is the eloqcl.ini file located in the etc subdirectory of your HP Eloquence installation, for example C:/Programs/Hewlett-Packard/HP Eloquence/etc/eloqcl.ini. For the 16bit dlgsrv, this is the eloq.ini file located in the Windows directory, for example C:/Windows/eloq.ini.

The default value is "netscape" which is the internal module name of the Netscape Navigator/Communicator. You can replace it with the module name of any HTML viewer which is aware of the "WWW_OpenURL" and "WWW_Activate" DDE topics.

For example, to use the MS Internet Explorer instead of the Netscape browser, just specify:

  HelpDDEModule=iexplore

Furthermore, you should specify an additional module path so the MS Internet Explorer can be started in case it's not already running. This is configured in the [Modules] section of the same configuration file:

  [modules]
  iexplore="C:\Program Files\Plus!\Microsoft Internet\Iexplore.exe"

Replace this with the real location of the MS Internet Explorer executable on your particular system.

Fixed problems

Setting a listbox's cy attribute to 0 resulted in a runtime error if the listbox was empty.
DLG SET ".focus" applied to a container object (dialog/window or groupbox) now sets the focus to the first sensitive object inside the container object.
If an object does not specify its own .help attribute the dlgsrv did not always fallback to the parent object's one.
The following problems concerning on-line help DDE communications have been fixed:
- "Module ... is not active and I don't know how to start it"
  If this message is displayed although the on-line help browser has started successfully, you can now configure an additional wait interval which takes place immediately after the browser is launched and before the first DDE transaction is initiated. This can be specified in the [DlgSrv] section of your HP Eloquence client configuration file:
  HelpDDEWait=2500
  The value is specified in milliseconds, thus 2500 is equivalent to 2.5 seconds.
  Please note that for technical reasons the HelpDDEWait configuration item has no effect with the 16bit dlgsrv. For the 32bit dlgsrv32 we decided to set the wait interval to 2.5 seconds by default which has proved to be appropriate in most cases, so normally it should not be necessary to configure HelpDDEWait at all.
- "DDE server did not acknowledge"
  If this message is displayed the internal DDE timeout has expired. While this was formerly set internally to 10 seconds it can now be configured in the [DlgSrv] section as well. Furthermore, the default value has been increased to 15 seconds:
  HelpDDETimeout=15000
  The value is specified in milliseconds, thus 15000 is equivalent to 15 seconds.
For the 32bit dlgsrv32, the client configuration file is named 'eloqcl.ini' and is located in the etc subdirectory of your HP Eloquence installation, for example C:/Programs/Hewlett-Packard/HP Eloquence/etc/eloqcl.ini. For the 16bit dlgsrv, it is named 'eloq.ini' and is located in the Windows directory, for example C:/Windows/eloq.ini.

RUN Server

The following changes have been included with the 16 and 32-bit runsrv on the Windows platform.

runsrv(32) accepts the command line option -port (or -PORT or /port or /PORT) followed by a service name or port number. This causes runsrv(32) to listen for incoming connections on a port different from the default service configured in the [RunSrv] section of the eloq.ini/eloqcl.ini configuration file.
This way, multiple instances of runsrv(32) can be run on the same system. For example, in Citrix Metaframe or MS Terminal Server environments multiple runsrv(32) instances can be run on the server, one for each user. To connect a user's program with the appropriate runsrv(32) instance, the A.06.31 eloqcore allows to specify the port number in a DLG SET ".driver" statement:
```
  DLG SET ".driver", "@hostname:port"
```
Such a multiple instance environment can be conveniently configured in the HP Eloquence eloq.ini file. For details, please refer to the section "New eloq.ini configuration file format" in the A.06.31 DLG driver release notes.
The following problems concerning DDE communications have been fixed:
- "Module ... is not active and I don't know how to start it"
  If this message is displayed although the DDE server application has started successfully, you can now configure an additional wait interval which takes place immediately after the DDE server application is launched and before the first DDE transaction is initiated. This can be specified in the [RunSrv] section of the eloqcl.ini configuration file:
  DDEWait=2500
  The value is specified in milliseconds, thus 2500 is equivalent to 2.5 seconds.
  Please note that for technical reasons the DDEWait configuration item has no effect with the 16bit runsrv. For the 32bit runsrv32 we decided to set the wait interval to 2.5 seconds by default which has proved to be appropriate in most cases, so normally it should not be necessary to configure DDEWait at all.
- "DDE server did not acknowledge"
  To avoid this message the internal DDE timeout default value has been increased to 15 seconds. Should this message persist you can change this timeout from within HP Eloquence with a statement like this:
  CALL DLL Run("RunSrv", hostname$, "DDE .TIMEOUT 30000", Errn, Msg$)
  For details, please refer to the A.06.20 release notes.
32-bit runsrv32:
The runsrv32 accepts a new configuration option in the [RunSrv] section of the eloqcl.ini configuration file:
```
  TrayDoubleClick=1
```
The Default value is 0. If set to 1 the runsrv tray icon must be doubleclicked to open the runsrv main window. If set to 0 a single click is sufficient (equivalent to previous runsrv versions).
If multiple programs have icons located in the tray it is inconvenient if some of them require single and others require double clicks. With this option, at least runsrv's behavior can be configured.