879.0.1
(Windows/ATE) A new (and rather cryptic) option has been added to the Settings..Misc menu to provide an option as to how the leading area (space between the rows, if any) is to be filled. Your choices are to select a fixed background color number, to opt for "auto" (specified as color -1) or "passive" (color -2). The fixed color is the simplest and will work nicely in applications which stick with a single background color (like a typical Windows app.) The main problem with this option is that if you pop up a colored box to display a message, the box gaps between the rows will show through.
The "auto" option fixes this problem by having A-Shell try to match the leading area to the row immediately above it. The main problem which this option occurs when you use a different color background for INFLD edits than for the rest of the screen, and you are using a GUI driver over ATE (in which case INFLD generates a superficial sunken effect around the field while you are editing it.) The problem is that the "auto" option for the leading fill color will cause the field to bleed into the leading area. This problem will go away when the true Windows control version of INFLD is available for ATE, but in the meantime, you may have to revert to one of the other leading fill options as a workaround.
The "passive" option tells A-Shell to not worry about refilling the leading area whenever the row above it is updated. This solves the problem with pseudo-GUI INFLD edits described above, but does not solve the problem with the gaps in rectangles using a different colored background than the rest of the screen. Note that the leading area will still get filled by certain screen clearing operations, such as TAB(-1,0) and TAB(-1,10); it just won't be updated by a local change in the background color of the adjacent row.
879.0.2
(ATE) LICENSE.LIT 2.0(106) (running on the server, with the /ATESRV switch) now interfaces better with ATE, causing the correct version and copyright message to appear on the ATE about box.
879.0.3
(ATE) A problem with "[DEMO]" appearing on an updated title bar even after licensing ATE via LICENS/ATESRV has been fixed.
879.0.4
(ATE) If there is a "fax" printer available on the local machine, ATE will add "<A-Shell FAX:> to the list of available printers, allowing you to use the A-Shell/Windows FAX: driver from the server. See the documentation on A-Shell/FAX in the Development Guide for more details on how to format documents for automatic faxing (without a user interface dialog).
879.0.5
(WINDOWS) A-Shell/Windows now determines its IP address on startup. In most cases, this will be invisible and painless, but if you have a software firewall (such as Zone Alarm) and/or a disfunctional internal DNS, the act of trying to determine the IP address may either trigger a hook in your firewall and/or cause a delay in launching an A-Shell session. A-Shell will automatically log the length of such a delay to the ashlog.log file if it exceeds 0.75 seconds, so if you notice a delay in launching A-Shell, you may want to check the log to confirm the source of the problem. (If we get too many complaints about this, we may make it yet another configurable option, but since the need to access DNS lookups is nearly ubiqitous now, we are optimistic that this will not be a problem.)
879.0.6
XCALL MIAMEX,128,IP$ returns your IP address.
879.0.7
Clean up and improve a number of error messages relating to socket problems (mainly for ATS mode). Nearly all errors now should be logged to the ashlog.log file (and NOT displayed on the server)!
879.0.8
(ATE) Now emulates some of the more common ZTERM ESC sequences, shown below. Note that most of these features are also available in A-Shell/Windows via a TAB(-10,x) sequence or an XCALL. The advantage of the TAB(-10,x) or XCALL method is that the same code will work under A-Shell/Windows and A-Shell/UNIX with ATE on the client. But the advantage of the ZTERM ESC sequences is that they would work on any server platform (i.e. one that you telnet to) provided the client is ZTERM or ATE. But in the latter case, you should test to make sure you aren't running locally on A-Shell/windows, where the ESC sequences would not make much sense.
EXECUTE OR PRINT WINDOWS FILE (aka "Shell Execute"):
?CHR(27) CHR(12);OP$;FSPEC$;CHR(0);
(OP$ is "O" to "open" or "P" to "print)
INPUT A ! CR for ok, Control-C for error
EXECUTE WINDOWS COMMAND (aka "Win Exec"):
?CHR(27);CHR(22);CMD$;CHR(0);
INPUT A ! CR for ok, Control-C for error
GET CLIENT IP ADDRESS:
?CHR(27);CHR(15);
INPUT "",IP'ADDR$
FTP FILE TRANSFER:
?CHR(27);CHR(1);CHR(127);DIR$;HOSTDIR$;CHR(0); &
HOSTFILE$;CHR(0);PCFILE$;CHR(0);
INPUT A
This uses the login name/password stored in the ATE configuration for the ftp name/password. The function to temporarily set a new name/password has not yet been implemented.
GET ZTERM/ATE ID:
?CHR(27);"?";
XCALL GET,BUFFER,0,2,RCVD,1000
IF RCVD<2 goto NOT'ATE'ZTERM
XCALL TINKEY,A$ ! extra char?
?CHR(27);"?";
XCALL GET,BUFFER,0,3,RCVD,1000
IF RCVD<2 goto NOT'ATE'ZTERM
XCALL TINKEY,A$ ! extra char?
?CHR(27);"?";
XCALL GET,BUFFER,0,2,RCVD,1000
IF RCVD<2 or BUFFER#"ZT" goto NOT'ATE'ZTERM
?CHR(27);"?";
XCALL GET,BUFFER,0,14,RCVD,200
? "VERSION=";BUFFER
Most AMxxx and WYxxx terminals will respond to ESC ? with 2 bytes indicating the cursor position (row and col each offset by 32). However, to be more robust, you should allow for the possibility that the terminal will not respond at all to ESC ?, or that it will give you an extra byte (possibly a trailing CR or a leading ^Y for columns > 96). The above code uses XCALL GET with the timeout option to input up to 2 chars, aborting after 1000 ms. It then uses TINKEY to grab any extra character without waiting. This sequence is repeated 4 times. After the 3rd time, ATE will respond with "ZT" (like ZTERM does). After the 4th time, it will return you "AV" following by the version string. (This is where you can distinguish ATE from ZTERM.)
879.0.9
EZVUE no longer escapes entirely when operator hits ESC while the help display is visible.
Also two additions to the list of EZSPL EXTOPT values. The complete set of options is now:
EXTOPT=###
Where ## can be a combination of the following:
Value |
Description |
|---|---|
0 |
Normal (upright) |
4 |
Disable screen save/restore |
32 |
Allow exit from EZVUE with left arrow |
64 |
Allow exit from EZVUE with TAB |
128 |
Allow exit from EZVUE with F1-F16 |
256 |
Don't ask questions on PRINT (see below) |
512 |
HOME when in HOME position prints. |
EXTOPT 256 is mainly useful in conjunction with the SBR=EZPRTX option in the MIAME.INI file, which causes EZVUE to XCALL EZPRTX instead of xcall SPOOL when printing from the viewer. Since you can customize EZPRTX.SBX, you may not want EZVUE to ask about starting and ending pages, or even about the printer choices. EXTOPT 512 is a bit obscure, but apparently there are some people who feel that hitting the HOME key right after launching the EZVUE viewer should act like the print command. Note that if you scroll down first, then the HOME key will take you to the home position (top of file).
879.0.10
Various improvements and fixes to VUE:
| • | Fix a bug in setting the file updated flag related to centering the screen and centering a line was causing VUE to warn you that the file had been updated (when it hadn't) or vice versa in some cases. |
| • | POP now restores the original screen position. Previously it positioned the window so that the popped line was the fifth line. |
| • | Implement primitive 'bookmarks': these are similar to the multiple push/pop capability except that there is no concept of a hierarchy or stack. ^SM creates a bookmark for the current line. ^SN jumps to the next bookmark. ^sC clears the bookmark from the current line. The feature is handy when working on several sections in a large file and you want to jump between them. |
| • | Implement the append macro feature (^_A). |
| • | ^_F formats the current paragraph. (Same as >FORMAT). |
| • | (UNIX, standalone mode) A new ini.vue feature, BAKDIR=<nativedirectory>, causes the .BAK file to be put in the specified directory, rather than in current directory. This can help avoid confusion in cases where .BAK files might not be recognized properly by other people or programs. |
| • | (standalone) The display of the file path on the status line is now more intelligent, expanding it out with the current dir info if not specified on the command line, and trimming the first part of it if too long. This is particularly helpful when simultaneously editing multiple copies of a file in different directories. |
