Please enable JavaScript to view this site.

A-Shell Development History

1182.7

EZTYP partial printing bug fix: page ranges starting with the first page were actually starting with the second page.

1182.6

EZTYP partial printing bug fix: for files containing hard form feeds, selecting a range of pages was resulting in an unwanted leading form feed on the first page, and typically one less page than requested.

1182.5

UNIX printing bug-fix: Restore original PRTCOPIES default of FALSE (matching the documentation). It was accidentally changed to TRUE in 5.1.1147 as a side-effect of a Windows printing enhancement.

1182.4

HOSTEX.SBR bug fix: Passing a "-g <icon>" clause on a "$ASHELL" command line (to launch a child session of A-Shell) was not working if the parent was launched with a "-g <icon>" switch. (It was reverting to the default acorn icon.)

1182.3

EZTYP bug fix: when using the P (print) option via the EZPRTX.SBX plug-in, after returning, an additional spurious request to print the entire file was being sent.

1182.2.1

EZ-SPOOL bug fix: accepting the default printer choice set by the application (in the XCALL SPOOL statement) in the BRIEF menu was resulting in the file being sent to the system default printer (i.e. as if you specified printer=""), rather than to the specified printer.

1182.2.2

XTREE bug fix: Combos using the "l" cformat type were returning exitcode 30 rather than 48 on exit. This problem was introduced with the Auto-Complete feature in 1181.0.

1182.1

MX_NXTCMD enhancement: Non-Destructive Read in MX_NXTCMD

1182.0.1

AMOS.SBR enhancement: new pflag value (+4) allows the child RUN program to pass its updated command file status to the parent. There are two main consequences. The first is that any command file inputs that were absorbed by the child program will not be available to the parent. (This is almost always preferable.) The second is that any attempt by the child program to CHAIN will effectively pass the chain information back to the parent, so that when the parent ENDS, it will then execute the chain requested by the child. (This may or may not be desirable, but it is the only way that an attempted CHAIN by the child will have any effect.)

1182.0.2

MX_FILESTATS enhancement: Owner and Group Info in MX_FILESTATS