APPX Server 4.2.2 Release Notes

The APPX 4.2.2 Patch Release addresses the following items:

  • Bug #838: SCAN is not Hookable
  • Bug #833: Client needs more control over Screen Fonts
  • Bug #829: PDF Reports fail on RISC platforms
  • Bug #821: 0LC - Hookable Processes HELP
  • Bug #817: Duplicated Toolbar AutoGui Buttons
  • Bug #810: DISAM restructure fails across file systems
  • Bug #755: Changing modes trips error in Pre-Display/Verify
  • Bug #673: Blank line generated before separator line in page heading

    •
  • Bug #669: Designer has no control over separator character
  • Bug #640: Separator character overwritten

  • Bug #617: PDF Output encounters c-assert if no records selected

  • Bug #517: PDF Output encounters c-assert if output has only a PAGE-START
    frame
Bug #838: SCAN is not Hookable

  • The 0LA Input processes are in 0LC to be copied and hooked. These are now hookable under 4.2.2. The list of input processes that make up the SCAN process family are:
    • NSCAN
    • NSCAN (110)
    • NSCAN (125)
    • NSCAN (30)
    • NSCAN (35)
    • NSCAN (50)
    • NSCAN (65)
    • NSCAN (80)
    • NSCAN (TOKEN) (15)
    • NSCAN (TOKEN) (35)
    • NSCAN FILE SELECT
    • NSCAN KEY VALUE
    • NSCAN PATH SELECT

Bug #833: Client needs more control over Screen Fonts

  • The -font= setting will let you use any OS or Java font as the base font used to compute all the screen geometry. 'fixed' and 'prop' are just shortcuts to reference 'Courier' and 'Helvetica'. In the prior versions of the client, Courier on linux really used a font called 'Lucida Sans Typewriter'. That was because of the way the Sun Java 1.2 and 1.3 VMs handled font names.
  • We now use Sun Java 1.4 which does honor Courier. So, if Courier is really not what you want, you should use a different real OS font name.
  • The list of available font names could be different on every system. So, the help with this the 4.2.2 client will dump the list of available fonts on a given system to the appxlog.txt file. It will also present a dropdown list in the Advanced Properties table of all the currently available OS fonts.

Bug #829: PDF Reports fail on RISC platforms

  • A report that utilizes standard page or standard column headings will fail if printed as a PDF-formatted report, but only on RISC platforms. This has been fixed.

Bug #821: 0LC - Hookable Processes HELP

  • When I Design transfer 0LC HELP and hook the process, I get an error:

Invalid Application ID

  • Offending code, per the EM Build Error Listing is:

Frame: Image: Child: START OF PROCESS
WRITE 0AD DOCUMENT

  • This has been fixed.

Bug #817: Duplicated Toolbar AutoGui Buttons

  • Sometimes the OK and Cancel buttons that show up on the toolbar are repeated 2 or three times on the toolbar. These are the buttons generated by the AutoGui STANDARD TOOLBARS process. It seems to be caused by having Direct Process 1 and/or Direct Process 2 active. This has been fixed.

Bug #810: DISAM restructure fails across file systems

  • If you restructure a DISAM file that is located in a different file system than the restructure work directory (Newdata), then the restructure will indicated that it ran successfully but the file will be missing. This has been fixed.

Bug #755: Changing modes trips error in Pre-Display/Verify

  • If an input process defaults to Inquire Mode, and you hit F12 to use Change Mode for key entry, it trips an error in my application in Pre-Display/Verify (looking to see if a field is blank). This has been fixed.

Bug #673: Blank line generated before separator line in page heading

  • If you specify a separator character, there is a blank line generated before the separator line. The only time it does not appear seems to be when there is no Page-Start frame. You get the blank line if there is a Page-Start frame even if you suppress printing by setting alternate image number to 0. This has been fixed.

Bug #669: Designer has no control over separator character

  • No matter what character you specify for the separator line (as long as it's non-blank), it prints as sort of a double underline character. This has been fixed.

Bug #640: Separator character overwritten

  • In the situation where a designer has requested standard column headings but has also designed a Page-Start frame, the separator character can get overwritten by the first line of data, and the designer-specified image is also overwritten by the GUI page heading. This has been fixed.

Bug #617: PDF Output encounters c-assert if no records selected

  • C-Assert: PDF_begin_page: Function must not be called in 'page' scope. This has been fixed.

Bug #517: PDF Output encounters c-assert if output has only a PAGE-START
frame

  • C-Assert: PDF_begin_page: Function must not be called in 'page' scope. This has been fixed.

Refer to the APPX 4.2.0 Release Notes for all enhancements and corrections built into this major release. Also refer to the APPX 4.2.1 Release Notes for items addressed by that patch release.