882.0.1
In INFLD, when INXCTL is a one byte string and the use transmits the new pseudo function key sequence (see item 2 under edit 881 below), INXCTL will return 250. (This allows these sequences to be distinguished from the normal IFX function sequences, which set INXCTL to 7.) This distinction is useful when the new pseudo-funkey sequences are used to encode mouse clicks, thus avoiding the need to start the mouse pseudo-funkey codes at some offset to avoid confusion over F-key generated function codes.
882.0.2
The INFLD edit control (|G) now uses the TYPE sequence |K to determine whether to adopt Windows-style or AMOS-style conventions whenever the two are in conflict. For example, without |K, the initial input mode is overwrite; with |K it is insert. (You can now use the INS key to toggle between insert and overwrite mode.) Without |K, the HOME key is considered a field exit key (returning EXITCODE 9 if TYPE 9 is specified); with |K, HOME just moves the cursor to the start of the field (but you can use CTRL-HOME to get the exitcode effect.
882.0.3
A bug introduced in 4.9, in which a RESUME from a BASIC error during a file read or write operation was causing an invalid syntax code or unsupported function error. The error was caused by the RESUME location being offset by one byte.
882.0.4
DPRINT now applies "intelligent justfication" logic to decide whether the field should be right, left or center justified. If both the first and last character of a string expression are spaces, then it center justifies. If the first character is a space or monetary symbol and the last character is a non-space, then it right justifies. Otherwise it left justifies. This should result in the desired alignment for data fields in most cases, although you may have to adjust any fields in which you were intentionally counting on the fixed width of spaces. In the proportional font world, you cannot count on spaces for positioning of text - always use explicit TAB(x,y) statements for each output token to avoid confusion.
882.0.5
(ATE 3.0.135) Function key translations were not working right with AIX. Also, ATE no longer displays "[DEMO]" on the title bar during the initial grace period while waiting for the server based license to be issued.
882.0.6
ATE.EXE now supports the ability to specify its initialization file on the command line, using the same syntax as for A-Shell (-i inifile). If not specified, the default is still ATE.INI, either in the same directory where ATE is launched from or from the directory above it. However, if that is not found, then it will try MIAME.INI in the same locations. (And the installer will not create ATE.INI if MIAME.INI already exists, thus by default ATE will share the same initialization file as an existing installation of A-Shell/Windows.) If the -i inifile switch is specified and doesn't contain a directory, the same directory search logic is used as for the default ATE.INI.
882.0.7
ASHW32 edit number is now appended to the ATE version number in its About box. (This is appropriate since other than the configuration dialogs, ATE is mainly all contained in ashw32.exe.)
