917.1.1
(ATE) Fix bug in processing ZTERM ESC sequence to paste clipboard (was waiting for an extra character.)
917.1.2
(Windows) Fix bug in MIAMEX,138 opcode 4 call (query Registry) call; was not expecting the TYPE parameter as documented. Now matches documentation (see edit 908 below).
917.1.3
(UNIX/ATE) Fix problem with server-issued ATE license being lost when using HOSTEX to launch a child A-Shell session.
917.1.4
(Windows/ATE) Fix problem where maximized setting in saved settings file was being overridden on startup if workstation not locally licensed.
917.0.1
LIT commands no longer generate an error when opening a file for output if the file already exists, unless the STRICT option is set (using OPTIONS=STRICT in the miame.ini, or SET STRICT).
917.0.2
(WINDOWS/ATE) Clear the default parent control setting (see MIAMEX,141) at the start of a new RUN program.
917.0.3
(WINDOWS/ATE) Various minor fixes and improvements in the AUI, "EVENTWAIT" operation. Define the various flags in the ashell.bsi (edit 108), including two new ones (EVW'DESCEND and EVW'SIBLINGS):
MAP1 EVWAIT'SYMBOLS ! [108] AUI,EVENTWAIT opcode flags
MAP2 EVW'NEXT,B,1,1 ! start with focus AFTER specified one
MAP2 EVW'NOWAIT,B,1,2 ! set focus and exit without waiting
MAP2 EVW'NOWRAP,B,1,4 ! exit at edge of range (instead of wrapping)
MAP2 EVW'NOFOCUS,B,1,8 ! no changes to focus
MAP2 EVW'NUMERIC,B,1,16 ! allow numeric keyboard input
MAP2 EVW'DESCEND,B,1,32 ! descend into subgroups of parent
MAP2 EVW'SIBLINGS,B,1,64 ! expand range to include siblings of parent
The EVW'DESCEND switch is needed when you want to allow the focus to be moved around a dialog or group that itself contains subgroups (such as a group of radio buttons). EVW'SIBLINGS expands the range of controls that the focus can be moved among to include siblings of the specified parent. An example where this would be handy is when you have a group of buttons in a dialog, and you want to start the focus on the first button in that group (without knowing the button's control ID), but you want to allow the user to TAB out of the button group into the rest of the dialog. It can be combined with EVW'DESCEND.
A new sample program, TSTEVW, is now available to help better understand both AUI,"EVENTWAIT" and BTNMNU.SBX (which is a wrapper for EVENTWAIT).
917.0.4
(WINDOWS/ATE) Bug fix: When checkboxes were created using the batch process (AUI,"CONTROL" opcode 8), they were always starting out unchecked. Now the initial checked state is based on the value of the control variable (as previously documented).
917.0.5
(WINDOWS/ATE) AUI "CONTROL" (aka MIAMEX,119) opcode 0 now returns all of the parameters relating to the actual control, rather than just the status. (It now returns the control text, type, coordinates, colors, font info, etc. The only field which is not returned is the checked status (func parameter), for which you need to use opcode 5. This is demonstrated in the TSTEVW sample.
917.0.6
(WINDOWS/ATE) Wallpaper is automatically turned off when in VUE.
917.0.7
(WINDOWS/ATE) Add a "Minimum Margin When Maximized" field to the Misc. Settings dialog to resolve the conflicts relating to adjusting the sizing of maximized windows. The normal, default setting is 0, which means that if the number of columns divides evenly into the screen width, when maximized there will be no left or right margin at all. (This happens, for example with 800x600 and 1280x1204 at 80 columns.) On some PC's however, this may cause the first and last column(s) to be clipped (due to overscan). Previously, we just subtracted a fudge factor from the screen width to prevent this problem, but now you can just set the minimum margin parameter. The margin units are pixels, but in most cases, setting the minimum margin to just 1 pixel will actually result in a considerably larger margin since font widths generally come only in integer pixel widths. For example, in the 800x600 case, the font width would be 10 pixels at 80 columns. But if you introduce a 1 pixel margin, the font width will have to be reduced to 9, which means that 80 columns only occupies 720 pixels (leaving a margin of 40 on either side).
Note that in the Windows and ATE environments, you can increase the number of columns in the window grid to put some of the margin space to work. For example, in the 800x600 case, if the font width is going to be 9 pixels, you could increase the number of columns from 80 to 88 and still a 4 pixel margin on either side.
The margin is ignored in non-maximized mode, because in that case, first of all, overscan is not likely to be a problem, and secondly, if it were, you could just adjust the window width with the mouse.
917.0.8
(ATE) When using xcall AMOS or xcall HOSTEX to launch another process on the server running A-Shell, if the ATE reverse channel socket is open, it will be automatically closed. (This allows the child process to establish its own reverse channel socket connection if it likes, and more importantly prevents messages which belong to the child from ending up going to the parent.) Upon return from the HOSTEX or AMOS call, the reverse channel is re-established, if applicable.
NOTE: the parent application is responsible for saving and restoring the screen. The recommended sequence is:
PRINT TAB(-1,202); TAB(-1,0); ! save screen & clear it
XCALL HOSTEX,"$ASHELL run prog" ! (or XCALL AMOS,"run prog")
PRINT TAB(-1,0);TAB(-1,203); ! clear and then restore it
