Please enable JavaScript to view this site.

A-Shell Development History

909.8.1

(Windows/ATE) New INFLD TYPE code ||g nullifies |G, ||G, and |g (in other words, deactivates the GUI enhancements.) This is useful when you have added |G to the global TYPE codes, but then want to disable it for a particular field.

909.8.2

(Windows/ATE) INFLD CMDFLG parameter may now be set to 2 to force a combo box or date picker control to start off with the dropdown box visible.

909.8.3

(ATE) ESC sequence for pasting text from the clipboard now works exactly like the Edit..Paste menu operation (except that the former provides an option of appending a CR). Previously there was a slight difference which may have resulted in garbage.

909.7.1

(PolyShell) New MIAME.INI command OPTIONS=TRKTOPSTS causes PolyShell to save/restore the top status line when swapping screens. Otherwise it only tracks the bottom status line and allows the top status line to be used for displays relating to the terminal or user, rather than the job.

909.7.2

(Windows) Fix bug causing bottom status line to become disabled if the top status line was removed.

909.7.3

(UNIX) Reinstate support for the -hetcki command line switch (that was lost somewhere along the line.)

909.7.4

Fix bug in compiler that generated a corrupted RUN file if a compiled statement used more than 1024 bytes of object code. (This was a rare case bug could occur, for example, with a long INPUT statement involving several dozen array values.)

909.7.5

DEVICE= statements in MIAME.INI now support quoted paths, allowing you to map a ppn to a path such as:

DEVICE=XYZ0:[1,1] "C:\Program Files\COOL.STF\ZTERM For Windows\"

909.7.6

(Windows/ATE) New MIAMEX function allows you to set the default parent control, to apply to subsequent TPRINT/DPRINT commands:

XCALL MIAMEX,141,CTRLID      (MX'AUTOPARENT=141)

This would be handy, for instance, if you wanted to use TPRINT statements to write on a TAB control or within a group box.

909.7.7

Implement XCALL MTMICR interface to the MagTek Excella Check scanner. (Contact us for details if interested.)

909.7.8

CMD/DO file processor now supports a variation of the: K command to input keyboard responses into variables which can tested in IF statements and used as DO file parameters. The following sample CMD file provides an example:

:R

:<Enter desired ppn: >

:K0

 

:S

:<Enter password: >

:K9

IF "$KBD9" = "SECRET"

DOLOG $KBD0

The special command: K0 is like: K, in that it waits for a line of input, but instead of passing the input to the current program, it simply stores it as $KBD0. The same concept applies to: K1 thru: K2 ($KBD1 thru $KBD9). The special $KBDn variables may be tested in an IF statement or passed as a command line argument to a DO file.

Note that when using $KBDn in an IF statement, it must be quoted (as in the example above.) However, when using it as a DO file command argument, it should not be quoted. (In the example above, the DO file DOLOG.DO will see the $KBD0 on its command line and convert it to whatever had been entered to the "Enter desired ppn" prompt.)

$KBDn variables cannot be used in any other context, even within a CMD/DO file. Unlike other special $xx variables which can appear in DO files, which are expanded by DO.LIT when it loads the DO file, the $KBD variables cannot be expanded until after the input operation takes place, and thus it is left to individual commands (currently just IF and DO) to interpret them.

This feature requires the following LIT file updates:

IF.LIT 1.0(106)

DO.LIT 2.1(121)

MDO.LIT 2.1(121)

909.7.9

DO.LIT 2.1(121) also supports the ability to specify the upper or lower case version of a $KBDn variable on the command line, which can be handy when building case-sensitive UNIX commands from input strings. The following example makes this clear:

;TEST.CMD

:<Input something >

:K1

DOTEST $KBD1 LCS($KBD1) UCS($KBD1)

 

;DOTEST.DO

:<Command line: $0 $1 $2

>

 

Assuming that the user had input "SiLly" in response to the prompt in TEST.CMD, the output of the DOTEST command would be:

Command line: SiLly silly SILLY

 

Note that these two functions - LCS($KBDn) and UCS($KBDn) are the only ones supported on the DO command line.

909.3

Note: there was gap in sequence numbers here. The previous build was 909.2, and the next one was 909.7. We just do this to see if you're paying attention.

909.2.1

(UNIX) Allow ^C from TCPX.SBR wait for accept operation.

909.2.2

Fix erroneous error 35 in parent program when SBX used MIAMEX,82.

909.2.3

Fix conflict between ANYCN and INFLD GUI mode. (Was generating a GPF or seg fault under some circumstances.)

909.2.4

Check for attempt to specify argument 0 in XGETARG or XPUTARG; if so, generate subscript out of range error (8). First legitimate argument is argument #1.

909.2.5

(UNIX) Fix problem in GET.SBR timeout feature in which it would not wait at all if doing keyboard input and the timeout setting was not at least 100 times greater (in ms) than the number of characters requested. (This was caused by a UNIX limitation of 1/10 second being the minimum usable setting for timed input.)

909.2.6

YANK <file> in VUE was not setting the file-updated flag, so if that's all you did and then tried to QUIT, it was not warning you that the file had changed.

909.2.7

(Windows/ATE) Fix a display anomaly with field attributes (when using the AM62CG driver with ATE or using OPTIONS=FIELDEMU) in which field TAB commands were not always occupying a space like they are supposed to.

909.2.8

(Windows/ATE) Remove warning about trying to define GUI objects if LATIN1 not set. We don't recommend using GUI objects unless LATIN1 is set, but apparently there are some legitimate situations where it might work.

909.2.9

(Windows/ATE) Don't check for MFT (manifest) files when executing LIT and SBX modules. This should speed up operations involving a large number of LITs (such as a batch compile using a CMD file with many IF, ENDIF, LOOKUP, etc.), or intensive use of SBX routines.

909.1.1

(ATE) Misc improvements and fixes to the new login options. See ATE release notes for 3.0.150

909.1.2

(Windows) INFLD no longer forces the A-Shell Window to get the focus when at the start of each field. (This behavior was introduced in build 899, but had the undesirable side effect of forcing A-Shell to the foreground even when it had just launched another window.) If reverting to the old behavior causes problems with A-Shell being hidden underneath other Windows when not appropriate, we may have to add a switch.

909.1

(ATE) Two new fields added to login configuration dialog:

"Wait for Login Prompt" option, if checked, causes ATE to wait for the ':' which normally terminates the "login:" and "password:" prompts before sending respective fields. If not checked, it waits for any group of characters followed by a pause (which tends to slow down the login slightly and also may not be quite as reliable in terms of matching the login and password fields up with their respective prompts.)

"Additional Login Text" field allows you to enter up to 255 characters (broken into however many commands), to be sent to the server after the password. Tildes (~) may be inserted in the text to cause a delay (each tilde counts for 250 ms). These can be useful in situations where there are timing issues in the application accepting the characters, or where the application may need to communicate with the client before dealing with the next keyboard command. (For example, the SET TERM command queries the terminal driver on the client for its ID, which is expected to be returned via the keyboard. Similarly, most of the ZTERM-compatible developer escape sequences use the keyboard channel to return status, as does the LICENS/ATESRV command and most other ATE commands. For any of these, you will need to insert delays if they are followed by any other characters in the list of "Additional login text".

909.2

(ATE) When starting a telnet session, if the FtpLocalDir field is defined in the profile, and there is an ATE.MDF file in that directory, then it will be processed for adding menus at the start of the telnet session. This provides a handy means of adding your own utilities to the ATE menu bar. Note that when the telnet session terminates, the menus are removed. (This is only an issue in the case where TELNET.LIT is used to launch a telnet session from within a normal A-Shell/Windows session, since in that case, the A-Shell window is not automatically closed at the end of the telnet session.)

909.3

(ATE) If the FtpLocalDir file in the profile is non-blank, an environment variable ATELOCALDIR is defined. This can be useful if you use this directory as place to keep files of interest to the server. Note that when using FTP, this directory will be the default, so the ATELOCALDIR is only really needed in conjunction with commands other than FTP.