Please enable JavaScript to view this site.

A-Shell Development History

Navigation: Version 6.5/7.0, builds 1600+ > 2018

1633 — 15 April 2018

Scroll Prev Top Next More

1633.5

Fix

ATE/ATSD AUXLOC printing refinement: a server-side printer init file containing DEVICE=PROMPT: will now be interpreted as DEVICE=AUXLOC:xxxxxx (where xxxxxx is the printer init file name), rather than DEVICE=AUXLOC:PROMPT: as it was before. Also, on the client side, ATE will look for an existing ASHCFG:PROMPT.PQI or SYS:PROMPT.INI in the case of DEVICE=PROMPT:. Both changes make it somewhat easier for the application to supply printer-independent configuration options in the printer init file that work even when the user selects a different printer from the Windows printer dialog.

1633.4

Fix

XGETARGSBX bug fix: was failing to support arrays passed byref.

1633.3

Fix

ATE refinement: client-side IATIMEOUT handler now recognizes screen output and other server-client messages as activity.

1633.2.2

Fix

SCALE bug fix: .IFELSE() function return value was getting upscaled twice. Same patch as 6.4.1557.2.

1633.2.1

Fix

XTREE print preview bug fix/refinement: extend the logic of the 1626.2 for the problem truncating the last character of some columns in the print version so that it also applies to the headers and footers. And, fix the problem where the headers became corrupted after exiting from the print preview display. (Same patch as 6.4.1557.2)

1633.1.2

Fix

XTREE bug fix: an error trap (Basic error #69) intended to handle an otherwise sticky ATE communication error was inadvertently being triggered for certain unrelated conditions.

1633.1.1

Fix

XTREE bug fix: failing to specify the FILIDX parameter for file-based mode was causing XTREE to crash.

1633.0.3

Fix

ATE-related improvements to handling of SIGHUP. Any call to AUI_EVENTWAIT, XTREE, XTEXT, INFLD, or any ATE command requiring a response, now trigger error 250. Previously, some of these operations were not being treated as input, causing delays or complications with an otherwise clean exit.

1633.0.2

Fix

Compiler edit 858: very long FOR statements were potentially failing to compile correctly due to an overflow, without triggering a compiler error.

1633.0.1

New

Collections enhancement: Writable Iterators