Change Notes for the JDLG 1.3.2.0 070806_1820 development snapshot
------------------------------------------------------------------

JDLG 1.3.2 comes with a new layout management to correct limitations
with resizing and scaling of dialogs.
If you encounter any problems with this release please send us a
problem report to jdlg@marxmeier.com.

Fixed problems in this release (relative to JDLG_1320_070801_1547):

- Fixed a problem with Pushbutton not correctly sizing when no width
  was specified. It was not properly accounting for insets.

- Fixed a problem with the Poptext rowdata attribute. An integer
  rowdata value was returned as string.

- The DLG DO statement could fail due to an interrupted exception 
  in JDLG.  

- Fixed a problem with Checkbox or Radio menu items on Windows.
  When switching the menu item state the specified font was 
  ignored in some cases.

- Changed the ProgressBar to no longer display post decimals. In
  previously versions the progress was output with two decimals.

- Added the system.lookandfeel attribute to return the currently
  selected look and feel. This attribute is readonly.

- Added the tabstop attribute (applicable to all controls) to specify
  if a control may receive the focus when iterating the dialog from 
  the keyboard (eg. using the TAB key).
  Supported values are 1 = yes, 0 = no. The default is 1.

  For example:
  DLG SET "Dialog.Button.tabstop",0
  
  This indicates the specified object is not reached by TAB but may
  be used with the mouse or a keyboard accelerator.

- Added the application.scalefactor attribute to allow specifying
  the scale factor of subsequently opened windows. The value is
  specified as a percentage, where 100 indicates a scale factor of 1.

  For example:
  DLG SET "application.scalefactor",150

  Indicates any subsequent dialogs should be scaled to 150%. This
  is independend of the selected scale mode for a dialog.


Known problems:

- In rare cases opening a window for the first time after starting
  a new session might display only the window frame but not its
  content. As a workaround the problem may be corrected by
  minimizing and then restoring the window.

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

- Changing the layoutpolicy of a dialog after maximizing may not work
  correctly.

- A maximized window that was made invisible and then visible again
  may have an incorrect "normal" size.