Change Notes for the JDLG 1.3.2.0 070706_1652 development snapshot
------------------------------------------------------------------

JDLG 1.3.2 implements a new layout management that is intended 
to handle resizing the dialog correctly. If you encounter any
problems with this release we would appreciate it if you could 
send us a problem report to the jdlg@marxmeier.com mail address.

Fixed problems in this release:

- On the Windows platform the dialog was redrawn on any DLG DO

- An unexpected function key event could trigger an exception, 
  resulting in an application hang

- Fixed a problem where deleting a list column would change the
  width of other columns

- Fixed a problem resulting in the listbox scroll bar to not be
  initially positioned in the leftmost position

- A DLG GET on the maxchars atttribute of an edittext object
  now returns zero instead of -1 of this attribute was not set
  previously

- Fixed a problem whith the rowdata attribute of a Listbox 
  object to return the value associated with the current
  cy if no index is present
  
- Fixed a problem with the rowdata attribute of the Listbox
  object to no longer cause an exception when the index is
  out of bounds. This condition now returns an error.

- An edittext may return a rule value if there is no other
  focussable object in the dialog.

- Fixed a layout problem with the GroupBox object when
  resizepolicy=scale was used

- Added a small offset to the border of a TabBox so the border
  no longer overlaps with child objects


Known problems:

- Restoring a window that was initially opened maximized may 
  move the window to the upper left or lower right corner in 
  some cases.

- When resizing a window that uses multiple fonts, some window 
  sizes may result in a subobtimal layout. This appears to be 
  caused a different aspect ratio, depending on the size.

- 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.