Change Notes for the JDLG 1.3.1.0 070525 1344 development snapshot
------------------------------------------------------------------

Fixed problems:

- A potential race condition was fixed that could cause JDLG
  to issue an exception message to the error log file if a
  ListBox was structurally modified.

- Additional diagnostics have been implemented which write to the
  error log file in case an object cache corruption is detected
  during DLG GET or DLG SET.

  If you encounter a cache corruption message in the error log
  file, please send us this message to the jdlg@marxmeier.com
  mail address. Thank you very much.

- The new diagnostic configuration "eloquence.config.diagGetSet"
  has been added. If set to yes (or true or on or 1) any error
  encountered as a DLG GET or DLG SET result is logged.

  In case of ERROR 657 ("Bad or improper attribute") the list
  of known attributes is output in addition.

  If you suspect that you encounter a DLG SET or DLG GET error
  without obvious reason, please send us a problem report including
  the full error log message to the jdlg@marxmeier.com mail address.
  Thank you very much.


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.