1. Function key translation modules are now loaded into user memory more or less like any other module or program. Previously they were loaded into memory but in a special area where they were invisible to MAP.LIT.
2. LOAD.LIT 2.2(107) no longer complains if it can't load COMMON.SBR. This annoyance was introduced in edit 106 of LOAD.LIT when it started actually "loading" arbitrary modules into user memory (as under AMOS.) But COMMON.SBR remains a special case; since the COMMON functionality and buffer space is embedded in A-Shell, loading the subroutine would no effect other than clearing any existing packets. LOAD.LIT has always done that (whenever the filespec being loaded was COMMON.SBR or when the /C switch was used) and continues to do so.
LOAD.LIT 2.2(108) has been adjusted slightly to account for the new handling of PFK and other function key translation modules. (Older version of LOAD will still work but may "double-load" such modules under the new A-Shell.)
3. DEL.LIT 2.2(107) similarly updated to not treat PFK and other function key translation modules specially. (The old versions of DEL, however, will still work, but may output redundant messages.)
4. (UNIX) Variables rows, via TAB(-5,x), now supported in TRACKER and in the AM65/AM75 drivers. Currently the support is like that under AMOS, i.e. only 24 and 42 rows are allowed. When ZTERM build 144 is released, we will probably enhance this support to take advantage of the ability to set any number of rows from 1-50.
5. SET.LIT 1.2(132) will now display the ZTERM build # in the SET TERM display (if applicable).
6. XCALL MIAMEX,13,TFLAGS {,OP {,ZTVER}} has been updated in two ways. First, as a side effect, it now forces A-Shell to probe for ZTERM. Second, there are two new optional parameters.
TFLAGS returns certain TRACKER-related flags:
TFLAGS |
Meaning |
|---|---|
1 |
132 column mode disabled |
2 |
color disabled |
4 |
field attributes on mode devices disabled |
8 |
force field emulation (Windows only) |
16 |
ZTERM has been detected |
32 |
ZTERM was probed for but not detected |
64 |
save/restore disabled |
OP may be specified as 0 to just retrieve the settings or 1 to retrieve and then update the settings. (If not specified, 1 is assumed.) When not specified or 1, the flags (and ZTVER) are updated from the specified parameters, and the original values are returned. (You can repeat the call a second time to reset the parameters back to their original values.)
ZTVER (S,10+) will receive the ZTERM build # if applicable. Note that the format will be something like "ZV2.0.143a". (The ZV prefix is constant for builds 74+.)
WARNING: The ZTERM probe may have the side effect of resetting the cursor to column 1 of the current row (or worse if the terminal device is not ZTERM.) So it is probably wise to issue this call when the cursor is already in column 1, and perhaps to even follow it by a TAB(-1,9) in case the probe caused some unwanted display characters.
SET TERM now uses this call.
7. INFLD.SBR now supports a new OPCODE flag (+32) for "read-only" mode. It has the same effect as TYPE "|r", e.g. it acts like an input call but the operator can not add to or change the field; they can only exit (with any of the allowed exit keys.) NOTE that in most cases, you would probably want to preload the field contents, so you would want OPCODE 33 (1+32) rather than 32 by itself.
Read-only mode may be useful is some exotic data entry situations (perhaps for reviewing previous entries with changes allowed only via an exit code/password/audit trail sequence.) In such a case, adding 32 to the OPCODE may be much easier to program than having to add/remove "|r" from the TYPE code string.
At the same time, a bug in read-only mode which allowed the use of ^D has been fixed.
8. The TRACE=MALLOC (SET TRACE MALLOC ON) tracing has been enhanced slightly.
9. New FLAGS value 256 added to PCKLST.SBR. When set, it disables the "auto adjust height" feature which is otherwise automatic.
