918.0.1
(Windows/ATE) Wallpaper is now turned off automatically while in VUE and EZVUE, and turned back on (if applicable) on exit. (Note that in the case of VUE, the restored wallpaper doesn't re-appear until you redraw the screen.) Wallpaper is also turned off when exiting A-Shell/UNIX.
918.0.2
(Windows/ATE) Introduce a new TCRT sequence to allow copies of the screen to be saved and restored in any order (as opposed to in LIFO stack order as with the existing TCRTs 202 and 203).
TAB(-10,40);"<cmd>,<id>";chr(127);
where <cmd> one of the following:
S (save screen)
R (restore previously saved screen)
P (pop previously saved screen without redisplay)
and <id> is an arbitrary numeric identifier from (1,2,3,...).
Examples:
? TAB(-10,40);"S,1";chr(127); ! save screen with ID 1
? TAB(-10,40);"S,5";chr(127); ! save screen with ID 5
? TAB(-10,40);"R,1";chr(127); ! restore screen saved as ID 1
? TAB(-10,40);"R,0";chr(127); ! same as TAB(-1,203)
! (i.e. restore last saved screen)
? TAB(-10,40);"P,3";chr(127); ! pop/discard screen saved as ID 3
? TAB(-10,40);"P,0";chr(127); ! pop/discard last saved screen
Notes:
This capability was implemented via a TAB(-10,x) sequence rather than by extending the existing TAB(-1,202) or TAB(-1,203) commands, because those commands to not have terminators and thus we cannot just add optional arguments. (Because TAB(-10,x) commands must be terminated with chr(127), they support variable length argument lists.)
TAB(-10,x) sequences are only supported under A-Shell/Windows and under UNIX when the client is ATE.
TAB(-10,40) does save and restore GUI controls. However, it is advisable that you clear the screen with TAB(-1,0) before restoring a saved screen which contains GUI controls; otherwise the restore controls will be added to any controls already existing on the screen.
Unlike TAB(-1,202) and TAB(-1,203), which operate on the machine where the software is running, TAB(-10,x) sequences operate on the workstation. Thus, under Linux, the save/restore operation takes place entirely on the workstation. This reduces both network traffic, memory, and CPU usage on the server, but it should be noted that the server's copy of the screen map will not be updated. This could interfere with server-based screen pictures, and also with the operation of TCRTs 202/203 after TAB(-10,40), since those TCRTs interact with the server's screen map. (The problem is temporary though, since the server's screen map gets re-synchronized whenever you clear and repaint the screen with regular, server-based PRINT statements.)
918.0.3
(UNIX) New miame.ini command OPTIONS=SEQLOK enables locking on sequential files (when LOKSER is enabled). Previously, sequential files under UNIX were not subject to locking rules (other than VUE, which implements its own locking scheme). Under Windows, sequential file locking has been enabled since 4.7.
