Change Notes for the JDLG_1320_071204_1349 development snapshot
---------------------------------------------------------------

Thank you for your interest and help in improving JDLG.

JDLG 1.3.2 comes with a new layout management algorithm to correct
limitations with resizing and scaling of dialogs. It also includes
a number of defect fixes as well as performance and functional
enhancements.

We expect it to shortly replace earlier JDLG versions.

If you encounter any problems with this release please send us a
problem report to jdlg@marxmeier.com.

New functionality:

- This version of JDLG implements initial printing support.

  JDLG printing support is intended to be used by an enhanced 
  version of eloqcore that supports redirecting PRINTER 10 to JDLG
  (eloqcore beta patch PE71-0711050 or newer, see below).

  JDLG implements new attributes related to printer job handling. 
  While these attributes may be used from an application they are 
  intended to be used internally by eloqcore.

  application.openprinter  
     This attribute may be used with DLG SET to open a print
     job. The string specifies the printer name, depending on 
     the JDLG platform conventions. An empty string argument
     specifies the default printer.
     
  application.closeprinter
     This attribute may be used with DLG SET to close a print
     job. The argument is ignored.

  application.print
     This attribute may be used with DLG SET to submit data to 
     an open print job.

  application.printerlasterror
     This attribute may be used with DLG GET to obtain additional
     information after a print failure. A string is returned.

  Please note that printer data is passed through and the printer 
  must be able to handle the data.

  Required eloqcore patch: PE71-0711050 or newer, available in
  the Eloquence B.07.10 beta patch download directory:
  http://eloquence.marxmeier.com/download/B0710/patch/beta/

  Please note that no eloqcore configuration is required to
  use PRINTER 10 with JDLG. If eloqcore is connected to JDLG,
  PRINTER 10 is automatically redirected through JDLG.

- Added the ComboBox maxchars and align attributes to mirror the
  equivalent EditText functionality.

  ComboBox.maxchars defines the maximum number of characters the
  ComboBox edit text may contain at any time.

  ComboBox.align allows to specify the text alignment within
  the ComboBox edit text. Possible values are "left", "center"
  and "right".
  
- PopText entries can now be selected by entering the leading
  letter of the entry to be selected.

- Added support for application logoicon to be used for POPUP
  BOX and as the default for the dialog icon.


Fixed problems in this release (relative to JDLG_1320_071128_1630):

- Multi-line EditText objects located in a GroupBox did not work
  as expected.

- DLG SET EditText.focus could remove the selection of the
  content if this EditText already had the focus.

- Selecting a ListBox line with the keyboard (SPACE, ENTER or
  selection by leading letter) could cause JDLG to hang in an
  endless loop if no line was selected.

- When the focus was put out of a ComboBox object, the ComboBox
  edit text's backgrounbd color could change. This was a side
  effect of introducing the ComboBox.focuscolor functionality.


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 suboptimal layout. This appears to be
  caused by a different aspect ratio, depending on the font sizes.

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