1501 – 06 January 2016

1501.5.2

Bug fix, MX_FIND: specifying the cdate/ctime parameters but not the udate/utime parameters was exposing a loophole which could lead to crashing A-Shell.

1501.5.1

XTREE refinement: Specifying the -$PRINT PopupMenu option was removing the print option from the popup menu, but it was not disabling the ability to print/preview using the built-in ^P command. To disable that, a new Advanced Coldef Option has been added:

Print=Disabled

Note that it doesn't really matter what follows the = sign; the only option is to disable since the default is for printing to be enabled.

1501.4

Bug fix: the .ash files were getting corrupted after repeated loading/ saving operations. Introduced in 1422.3; problem can be corrected by re-saving with this version.

1501.3

Print filter refinement: filter SBX names can now be up to ten characters; previously was six.

1501.2.3

Bug fix, XTREE: when using XTROP_REPLACE to effectively add rows, after previously deleting rows, the new rows were being added properly.

1501.2.2

ATE server-side refinement: increase the wait time on the initial handshake from 3 to 6 seconds. Some large systems with slow/congested/remote networks were occasionally hitting the timeout, causing the session to not recognize that the terminal was ATE.

1501.2.1

Bug fix, INPUT #CH: When the last line of the input file was longer than for i the input variable, if the variable was followed by the byte sequence chr(26) chr(0), the chr(26) was getting set to null. The bug has been there for years, but probably went unnoticed because the conditions for it were fairly rare.

1501.1

Bug fix, XTREE: When editing "#." and "#," fields, the number pad keys were being rejected. The regular number keys were fine.

1501.0.2

Bug fix / enhancement: Selecting bold option in the system fixed pitch font selection dialog now affects the resulting font.

1501.0.1

New SIZE.SBR Parameter FLAGS.

1501.0.1

Bug fix, SCALE: with .ISNULL(), .LINENO(), .PAGENO(): the results weren't being SCALEd, which would have been a problem when combining with the unary NOT operator, i.e. NOT .ISNULL(var). Only affect programs with an explicit SCALE value.