|
1550.6 |
06 June 2016 | |
|
1550.6 |
Fix |
Compiler edit 805, OUTPUTONLY: The :OUTPUTONLY modifier on function and procedure parameters was not preventing the parameter from being updated by the caller on input, except for the first :OUTPUTONLY parameter of each function. |
|
22 May 2016 | ||
|
1550.5.2 |
Revision |
Windows Password refinement: stifle the CAPS LOCK warning bubble if the force upper case option is enabled (type "^" or "|u"). |
|
1550.5.1 |
Fix |
MX_PWCRYPT: adjust the internal limit on the size of the seed parameter (was 21) to match the length specified in the documentation (64). |
|
1550.4 |
18 May 2017 | |
|
1550.4.1 |
Fix |
Error message formatting: The location counter in BASIC error messages was being replaced by the terminal device when one or more of the relevant coded messages in ERRMSG.xxx were missing. |
|
1550.4.2 |
Fix |
(Linux) WHI catalog library update (MPS.SBR) to 48.5.1.2 |
|
18 May 2017 | ||
|
1150.3 |
Fix |
ATE: close a loophole where it was somehow possible for the SFTP port to get out of sync with the SSH port even though the "Link to Transport / Login Settings" option in the ATE File Transfer configuration was set. |
|
1550.2 |
16 May 2017 | |
|
1550.x |
Fix |
Restore support for non-PFX translation tables that are neither IFX (INFLD) nor VUX (VUE); this was inadvertently dropped in 6.1.1402.5. |
|
1550.1 |
15 May 2017 | |
|
1550.1 |
Fix |
File name conversion: trailing spaces on the main part of AMOS-compatible filenames (e.g. "CUS .DAT") were being preserved in the conversion to the native equivalent. This may make logical sense, but was an unexpected deviation from the way it used to work in 6.2 and prior. Since spaces were not allowed in AMOS filenames, names like "CUS .DAT" were, and now are, treated as "CUS.DAT." |
|
1550.0 |
14 May 2017 | |
|
1550.0.1 |
Fix |
MSGBOX.SBR: passing the new mxflags parameter without passing the subsequent parameters thru iconspec may have crashed A-Shell. |
|
1550.0.2 |
Fix |
INPUT {CSV}: revise the 1548.9 patch which was causing unquoted comma delimiters to be interpreted at decimal separators if the LDF so specified. Numeric values with comma decimals must be quoted in such a case, e.g. "1,23". |