Line: 1 to 1 | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
APPX 6.0.0 Features
| |||||||||||||||||||
Line: 30 to 31 | |||||||||||||||||||
If a Group field contains a Unicode field, you cannot SET that group to or from an Alpha field. The process will give an 'Invalid Storage Type' compile error. Similarly, Unicode fields cannot be set into a Group field. This may have an impact on your applications if you are using --- TEMP fields to move data to/from a group, since all --- TEMP fields are Unicode. You can use one of the new WORK RAW fields instead. If a group field contains a Unicode field, it can only be moved to/from another group field. | |||||||||||||||||||
Added: | |||||||||||||||||||
> > | There are many new fields on the GUI Attributes screens for Items on an Image. Because of this, we recommend using at least 27 rows in your Desktop Client setting. | ||||||||||||||||||
There are additional considerations discussed in more detail at the end of the Upgrade instructions.
Changes in Release 6.0 | |||||||||||||||||||
Line: 37 to 40 | |||||||||||||||||||
Here is a list of the changes in Release 6.0:
Unicode | |||||||||||||||||||
Changed: | |||||||||||||||||||
< < | You can now specify a 'Unicode' encoding type for Alpha and Text fields. This is in the Additional Attributes dialog box: | ||||||||||||||||||
> > | You can now specify a 'Unicode' encoding type for Alpha and Text fields. This is speicifed in the Additional Attributes dialog box: | ||||||||||||||||||
Line: 47 to 50 | |||||||||||||||||||
If the new record length is > 32K, you will get a warning from the Data Dictionary compiler. If you are going to store this file in Oracle or SQL Server, you can ignore this, however, the 32k limit still applies to APPX/IO files. | |||||||||||||||||||
Changed: | |||||||||||||||||||
< < | In order to display or print Unicode data, the field must have GUI Attribute of either a LABEL (non modifiable field or Output) or RAW TEXT. The default font for a LABEL is Arial, which may be noticeable if the other fields are not. You can override the default font to COURIER to use the same font as fields without a GUI attribute. | ||||||||||||||||||
> > | In order to display or print Unicode data, the field must have GUI Attribute of either a LABEL (non modifiable field on an Input or normal field on an Output) or RAW TEXT. The default font for a LABEL is Arial, which may be noticeable if the other fields on the image are not. You can override the default font to COURIER to use the same font as fields without a GUI attribute. | ||||||||||||||||||
You also need to consider how this field is used. If it is moved to a non Unicode field (via SET, RECEIVE, etc) that will cause a runtime error to occur if the source field contains Unicode characters that cannot be transcoded. To prevent this, all target fields must also be Unicode and any fields they are moved to, and so on.
New & Revised API's | |||||||||||||||||||
Added: | |||||||||||||||||||
> > | All the .TEXT API's have been reworked to accept Unicode strings up to 1M in length. The .TEXT LOWER TO UPPER and .TEXT UPPER TO LOWER use the Unicode library to convert text. If you have applications that add or subtract 32 from the ASCII value to convert case, be aware this technique will not work with Unicode data (unless the Unicode field only contains US ASCII characters). The .STREAM functions have been reworked to read or write data in UTF-8 format. The following API's were added: .TEXT FROM UNICODE - transcodes a Unicode field to a Raw field, with control over characters that can't be transcoded. .TEXT GET UNINAME - returns the name of the Unicode character. .TEXT SET UNINAME - sets a Unicode character by name. .TEXT TO UNICODE - transcodes a Raw field to a Unicode field. .TEXT UNICODE COMP - compares 2 Unicode fields. | ||||||||||||||||||
New Widget fields | |||||||||||||||||||
Added: | |||||||||||||||||||
> > |
There were a number of GUI capabilities that were only accessible via macros (@xxx=yy). The following macros have been converted to formal WIDGET specifications:
@SDS - Drop Shadows @SLN - Layering @SFP - Focus Painting @SMV - Movable @SLUB, @SSPO - Line settings @TSRN - Show Row Numbers on Tables (HTML client only) @TSFB - Show footer bar on Tables (HTML client only) @TCSS - Case Sensitive Sorting on Tables (HTML client only) @FULC - Suppress use of Local Connector (HTML client only) The migration utility will convert the macro to the formal specification when it can and the macros still work if you prefer those. Here is a sample GUI Attributes screen showing some of the new fields: We recommend running with at least 27 rows to accommodate the larger Property screens. The following fields have been added to --- WIDGET and can be manipulated via ILF: Drop Shadows WIDGET DS VISIBLE WIDGET DS DISTANCE WIDGET DS ANGLE WIDGET DS OPACITY WIDGET DS SIZE WIDGET COLOR DS (Group Header) WIDGET COLOR DS R WIDGET COLOR DS G WIDGET COLOR DS B WIDGET COLOR DS NL Layering WIDGET LAYER NO Focus Painting WIDGET FOCUS PAINTED Moveable WIDGET MOVE OPTION NO Line Settings WIDGET LINE BASE NUM WIDGET LINE STROKE OFF HTML Client Table Settings WIDGET TAB SHOW ROW NO WIDGET TAB SHOW FOOTER WIDGET CASE SENSITIVE HTML Client Local Connector Control WIDGET SUPPRESS LC Consult the online manual at APPX Multi-Release Application Design Manual for details on the Widget specifications, or use the Help key while in Application Design. | ||||||||||||||||||
New TRAP control | |||||||||||||||||||
Added: | |||||||||||||||||||
> > | You can now turn TRAPs on or off in an individual process. When you invoke a process, there is a new TRAP Control button: If you click the TRAP Control button, you will get some choices: The options are self explanatory. The system identifies 'your' TRAPs by checking the user id of the user that added the TRAP and the date. Anything you added today will be considered 'your' TRAPs. TRAPs you added in the past, or TRAPs added by other designers are not considered 'your' TRAPs. The method of turning off TRAPs has been changed as well. Previously, APPX would convert the TRAP to a comment statement, making it awkward to activate the TRAP later. Now it will check the TF flags, and as long as there is one available flag, it will simply comment the TRAP, making it easier for you to uncomment it later. This option is also available in the Toolbar and Toolbox pulldown menu while at the Process level: | ||||||||||||||||||
New flag to suppress PDF Dialog box | |||||||||||||||||||
Added: | |||||||||||||||||||
> > | A new flag has been added to the System Parameters to allow you to suppress the PDF Confirmation Dialog box: Normally when a PDF document is produced and the 'Print on Screen' flag is checked the document will be uploaded to the user's desktop. At that point, a PDF Confirmation Dialog box will appear and the user can continue to the next job step or choose to cancel the job. In many cases, this is unnecessary. You can check this box to globally skip this dialog box. | ||||||||||||||||||
Jump to process from audit history | |||||||||||||||||||
Added: | |||||||||||||||||||
> > | While viewing Audit History in Application Design, you can jump to that process/file/field: The Audit Browser only shows the process information, but if the change was actually made at the Image level, the Jump button will take you to that Image. | ||||||||||||||||||
Jump to O/C from Button GA | |||||||||||||||||||
Changed: | |||||||||||||||||||
< < | New Font type Resource | ||||||||||||||||||
> > |
While viewing the GUI Attributes of a Button, you can Jump to the Optional Child specified by the button:
In this example, clicking the 'Children' button in the Toolbar will take you to Optional Child 1, since the button fires USER 1.
New Font - ResourceA new Font Type of 'RESOURCE' is available.: Choosing this font type will cause APPX to use the font specified by the Named Resource. If you choose this font type, you must also enter a Named Resource. This replaces the technique described where you have to read the WIDGET record and indirectly set WIDGET FONT to 10 via ILF. Now you can simply choose the font RESOURCE. | ||||||||||||||||||
New utility to check for dup shortcuts | |||||||||||||||||||
Added: | |||||||||||||||||||
> > | A new utility has been added to the 'Tools' tab in Application Design - 'Check for Dup Shortcuts'. It will list all the shortcuts used in the application and flag the ones it thinks might be duplicates: In this example, the letter S is used for both the 'Save' button and the 'Sales Opport.' button and W is used for both 'Weather' and the WWW button. | ||||||||||||||||||
0LA Output STANDARD MOD LOG and 0LA Input CONFIRMATION (END) in 0LC and can be hooked | |||||||||||||||||||
Added: | |||||||||||||||||||
> > | The Output STANDARD MOD LOG and the Input CONFIRMATION (END) have been added to application 0LC and can now be hooked. | ||||||||||||||||||
Bugs Fixed | |||||||||||||||||||
Added: | |||||||||||||||||||
> > | The following bugs were addressed in this Release:
Field and Domain with same name share token values (#2947) RBS - Copying at the Workgroup level doesn't work (#4102) RBS - Multiple Roles with same name & same user (#4103) Duplicate 'T' shortcuts in 'Enter / Edit Translations' (#4108) | ||||||||||||||||||
Known IssuesAPPX/ODBC is not available yet | |||||||||||||||||||
Line: 77 to 195 | |||||||||||||||||||
-- JeanNeron - 2018-02-20
| |||||||||||||||||||
Added: | |||||||||||||||||||
> > |
|