Uniface 9.7.01 Patch G101 available for W32, W64, LIB, RSD, A82, SO9, HPK, HPM, LU6 and VI1

Author: daniel.iseli@uniface.com (diseli)

Uniface 9.7.01 patch G101 has been released and is available for W32, W64, LIB, RSD, A82, SO9, HPK, HPM, LU6 and VI1 on Uniface Downloads: https://download.uniface.com/downloads/Uniface/patches/9701/ The information about the included bug fixes can be found shortly on the page with the Patch Listing for release 9.7.01 - or in the ReadMe of the Patch (e.g. https://download.uniface.com/downloads/Uniface/patches/9701/w32/w32g101.txt). Please note that you must have a user account to access the Service Pack on the Uniface Downloads site. To receive an account, you will have to register first. User accounts are currently NOT linked to other Uniface sites such as Uniface.info.

1 Comment

  1. Updates for G101:

    • When the binding type is Document/Literal Bare, the developer provides the document, element, and contents for IN parameters and OUT parameters. For other binding styles, Uniface applies certain rules for how complex data should be provided in parameters.
    • The following fields in the UROUTMON model have been enlarged from C80 to C256 characters to allow for long host names, as often used in cloud-based environments.
    • Compiler error -1054 is generated if an entity frame is positioned below a break frame or trailer frame.
    • forentity returns error -1102 if the EntityName parameter is incorrect or the entity is not included in the component structure.
    • The documentation has been updated with information about the psdef.txt file, which is used to configure PostScript printing on Unix.
    • The timeout values specified by the cto and rto SOAP connection options are also applied when reading the WSDL file prior to sending a SOAP request.
    • The default request timeout for the rto SOAP connector option is now 30,000 milliseconds for both the SOP 1.0 and SOP 2,0 connectors.
    • The default connection timeout for the cto SOAP connector option is now 30,000 milliseconds for both the SOP 1.0 and SOP 2,0 connectors.
    • Any popup form that does not fit the screen will be clipped. Note: This is a change in behavior. In previous versions of Uniface, when a popup form did not fit, it was centered on the screen, which disconnecting it from its anchor or field. A popup form with a title bar opens according to its Position property but will not move with its anchor. If the parent field, rectangle, or form is moved, the opened popup form with title bar stays where it is. It does not move with its parent field. This is contrast to other popup forms, which remain with the parent field and move with it when the field or form is moved.
    • Even when the Input Method Editor (IME) is enabled, either by setting AutIoImeOpen=on or setting the field syntax to YIME, the IME is disabled fields the field syntax NDI (do not display contents). For Unifields that have the IME enabled, the IME remains enabled even when the syntax is NDI. Note: In fixing this issue, some behavior changes have been introduced when the IME is enabled:
      • When the field syntax is set to NPR, the IME remains enabled.,/li>
      • When the field syntax of a Unifield is set to NDI, the IME remains enabled.
      • When the field syntax of a Unifield is set to NED using $fieldsyntax (or fieldsyntax), the IME is disabled
    • For a Checkbox widget in a static server page (USP), Uniface now maps a Null (empty) value in the data to a False value in the HTML. As a result, the behavior of the Checkbox in retrieve profiles has changed. A retrieve profile that includes the Checkbox can retrieve only True or only False values. To retrieve data the contains both True or False values, the value of the checkbox field must be set to null in Proc. Prior to this fix, an empty Checkbox retrieved both True and Null values, but not False values.
    • For List, Menu, and RadioButton widgets in USPs, the format of values in the ValRep list must be same as the display format of the field.
    • It is not possible to directly compare two parameters, variables, or fields that use the data type raw or image—they will always evaluate to True. An alternative is to calculate and compare a hash of the data.
    • There are compatibility issues when combining the new styling properties for area frames and entity frames with the existing Border and Color properties.
      • If both the Border and BorderType properties are set, two borders are displayed. Only a flat BorderType can be styled.
      • If Color is set, all properties set in the initialization file are ignored, including BorderType and colors.
      To prevent these issues in existing components, it is recommended that you use the new properties only for new and modified components, and for new named area frames. When modifying a component to use the new properties for an entity or area frame, it is recommended that you set Color to No and turn Border off. For an entity, remove all entity property values set in the Entity Properties dialog. Tip: More information on using entity and area frame properties is available in blogs and downloads on uniface.info.
    • The usysparm function can be used to get the value of the $dberrortext Proc function.
    • The documentation for the JavaScript API functions for getting and setting the text of a label has been corrected. The functions are setValue and getValue.

    For details see the updated Uniface Library provided with the patch G101 or the latest version of the documentation for Uniface 9.7 (Patch G101) that will be available online here on Uniface.info.

    Author: diseli (daniel.iseli@uniface.com)