Change Notes for the JDLG 1.3.1.0 070423 1311 development snapshot
------------------------------------------------------------------

Fixed problems:

- DLG DRAW and DLG SET Dialog.do,1 did not correctly put a dialog
  into foreground if it was previously invisible or not the fore-
  most dialog of the session.

- A dialog that is activated with DLG SET Dialog.do,1 did not
  behave as expected. It was not always put into foreground (see
  above). Also, clicking a push button sometimes had no effect.

- DLG GET HtmlView.content caused JDLG to hang due to an internal
  ClassCastException.

- JDLG isues a communication error message box if the network
  connection to the program is reset, e.g., when the program is
  killed. Clicking the OK button in this message box sometimes
  had no effect. This should no longer happen. In addition, for
  convenience the message box is now automatically closed after
  5 seconds if the user does not click the OK button.


Known problems:

- On Windows, EditText objects that are set .sensitive = 0 may not
  correctly indicate its disabled state (i.e., not being greyed out).
  This happens due to a bug in Java Swing that unfortunately has not
  been solved until today (as of Java 1.6). Unfortunately, there is
  no workaround available in JDLG. For details, please refer to the
  following Sun Java bug database entries:
  http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5042122
  http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4883120
  http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4853457

- If the Window menu has multiple identical entries they are not
  distinguished. The first entry is always activated regardless which
  entry is clicked. This has always been a bug in JDLG and will be
  solved in a future release.


Please note:

- JDLG 1.3.1 implements a new focus/rule manager. If you encounter any
  problems with this release we would appreciate if you could send us a
  problem report to the jdlg@marxmeier.com mail address.
  Thank you very much.