A-Shell Development History

1713.4.2

Fix

Close JOBTBL corruption loophole: ATE and A-Shell instances launched from the same machine no longer share the same instance counting pool, eliminating a loophole where the overlapping disconnect of an ATE session and startup of an A-Shell session could result in two A-Shell instances getting assigned the same job number, with one zapping the other. And in the case where two sessions do try to share a job, one will be terminated after a minute or two of logged warnings, rather than logging warning messages endlessly.

1713.3

EIR

XTREE: cformat code A (ASCII sort) now takes precedence over code # (numeric).

1713.2

Fix

AUI_CONTROL: the MBF_CENTER options were interfering with the MBF2_DLGSTATE flag, causing a previously saved maximized state to be reset back to normal size.

1713.1

Fix

XTREE: when using XTROP_REPLACE to add rows to an existing tree whose font scale had been adjusted manually (using Ctrl +/-), the new rows now start with the adjusted font size. Previously they were starting with the default font size.

1713.0.1

New

Language enhancement, compiler edit 977: New system function TRIM(strexp), or TRIM$(strexp). This removes the leading and trailing blanks from the string expression argument, equivalent to the combination of STRIP$(strexp) and LSTRIP$(strexp). Besides offering the advantage of functional syntax, as a built-in function, TRIM$() is more efficient than the equivalent XCALL TRIM (although the latter offers an additional option to remove other characters besides blanks).

1713.0.2

Fix

XTREE: multi-column sorts specified interactively (using CTRL+ click on the column headers) were not being saved correctly by the XTR'USRCFG feature. The column precedence was reversed.

1713.0.3

Fix

XTREE: the XTF_EDITABLE flag was disabling the initial sort when the opcode was XTROP_RESELECT and the XTF_NOREDRAW flag was not set.

1713.0.4

New

XTREE enhancement: new PopupMenu Command $SORT triggers an internal multi-level sort.

1713.0.5

Fix

XTREE: close a loophole in which the saved and restored column widths (see XTR'USRCFG) were getting over-ridden by a subsequence column optimization operation during certain re-entry scenarios. One such scenario was when row headers were enabled.