Eloquence JDLG 1.5 ================== Revision: 1.5.7-120514-1914 2012-05-14 JDLG 1.5.0 was released in July 2009. Release history: - JDLG 1.5.1 (August 2009): Bug fixes - JDLG 1.5.2 (October 2009): Enhancements and bug fixes - JDLG 1.5.3 (October 2009): Bug fixes - JDLG 1.5.4 (November 2009): Enhancements and bug fixes - JDLG 1.5.5 (March 2010): Enhancements and bug fixes - JDLG 1.5.6 (August 2010): Bug fixes - JDLG 1.5.7 (December 2010): Enhancements and bug fixes - JDLG 1.5.7-110128-1437 (January 2011): Enhancement - JDLG 1.5.7-110429-1914 (April 2011): Enhancement - JDLG 1.5.7-110518-1310 (May 2011): Enhancements - JDLG 1.5.7-110526-1229 (May 2011): Bug fix - JDLG 1.5.7-110705-1228 (July 2011): Bug fix - JDLG 1.5.7-120514-1914 (May 2012): Bug fix Documentation: http://eloquence.marxmeier.com/doc/jdlg/ Recent changes -------------- Changes in JDLG version 1.5.7-120514-1914: - Fixed a problem where an image did not change if the same URL was used to load a different image (#4074). Changes in JDLG version 1.5.7-110705-1228: - Fixed a problem related to the GroupBox scroll position if multiple scrollable GroupBoxes are nested. Setting the focus to an object located in a nested scrollable GroupBox could set the scroll bars of an outer GroupBox to a wrong position. Changes in JDLG version 1.5.7-110526-1229: - Fixed an incompatibility with Java versions before 1.6, potentially causing a java.lang.NoSuchMethodError: java/lang/String.isEmpty()Z Changes in JDLG version 1.5.7-110518-1310: - Added the eloquence.config.typeahead configuration property and the corresponding System.typeahead attribute. The typeahead function prevents characters from being lost if they are typed while an EditText or ComboBox object has the focus but the Dialog is not interactive, i.e., currently outside DLG DO. The typeahead function is enabled by default. - Added the global System.clipboardcontextmenu attribute, the session- specific Application.clipboardcontextmenu attribute and the object- specific common clipboardcontextmenu attribute. - Changed the default of the eloquence.config.notifybusy configuration property. The default is now: notifybusy = yes Changes in JDLG version 1.5.7-110429-1914: - Added the eloquence.config.keepalive configuration property. The eloquence.config.keepalive property specifies the keepalive interval in seconds. If nonzero, JDLG sends keepalive messages in the specified interval during a DLG DO or POPUP BOX invocation. This allows eloqcore to detect whether a JDLG connection is still active or was interrupted. The latter case is assumed if eloqcore does not receive any message from JDLG for five times the specified interval during a DLG DO or POPUP BOX invocation. If an interrupted JDLG connection is detected, the connection is closed and ERROR 684 is returned to the program. This function may also be useful to solve idle timeout problems caused by network router/firewall configuration. A network router might be configured to close a connection if it has been inactive for some time. To prevent this from affecting JDLG connections, a JDLG keepalive interval could be configured. For example, assumed the router idle timeout is 30 minutes, an eloquence.config.keepalive=900 configuration would cause JDLG to send a keepalive message every 15 minutes so that the router idle timeout would not expire. Notes: * The eloquence.config.keepalive configuration requires an eloqcore version which supports the keepalive functionality, otherwise it has no effect. For Eloquence 8.0 this requires eloqcore patch PE80-1104280 or newer. For Eloquence 8.10 this requires eloqcore patch PE81-1104280 or newer. * Instead of configuring the eloquence.config.keepalive property, a program may invoke DLG SET ".keepalive",Seconds to specify the keepalive interval, for example: DLG SET ".keepalive",900 Changes in JDLG version 1.5.7-110128-1437: - Added the System.activate attribute. If multiple sessions are active, DLG SET System.activate brings the dialog of a concurrent session into foreground where the dialog title matches the specified string argument, similar to clicking an entry in the Window menu. Known issues ------------ - When the user hovers the mouse cursor over the divider of a Splitter or ListBox column header, the mouse cursor may not change appropriately in some cases. - Moving a Dialog so that it violates the screen boundaries may unexpectedly change the reference point in some cases. - On the Linux platform, the space used by the Desktop task bar or the Desktop menu bar may not be properly accounted for. This is caused by a Java Swing limitation, where the necessary information is not available. This should have little consequences besides that JDLG cannot ensure that a Dialog window is not obscured by Desktop elements. - On platforms where JDLG runs on top of an X11 window manager, such as Linux, the content of the X11 clipboard may change when the content of an EditText or ComboBox object is selected. This is Java behavior which cannot be affected by JDLG.