1194.4.1 |
MX_WINSETTINGS refinement: Opcode 1 (set value) is now much faster (under ATE) due to the elimination of the need to wait for a response from the ATE client. |
1194.4.1 |
MX_WINSETTINGS / AW_WINSETTINGS refinement: Opcode 0 (get value) with id 0 now returns a comma-delimited string of all the available values. (This is much faster than retrieving each value one at a time over ATE, where there could be a several ms latency for each command/response turnaround.) Note that the comma-delimited string will have a place for each setting by ID value, from 1 to the maximum ID (currently 21). |
1194.4.1 |
AG_XFUNCS bug fix: SBX routines that were themselves invoking AG_xxx functions (either directly or indirectly via MX_xxx functions) were sometimes causing ATE to hang due to a conflict in handling the nesting of commands. This should be fixed now. |
1194.4.1 |
XTREE bug fix: A recent fix had the side effect of breaking certain XTREE exitcodes. |
|
COMIO bug fix: Inputting (opcode 8) up to a specific terminating character (e.g. COUNT=-1 to input up to a CR) was having the side effect of removing all the remaining characters from the input buffer. (This was introduced in one of the recent updates.) Also, opcode 16 (write) now returns (in COUNT) the number of characters actually sent, per the documentation. |
1194.2.1 |
ATE command bug fix: Some commands with very large responses (over 2K), such as a request to retrieve clipboard data (using MX_CLIPBOARD) were leading to a buffer overflow and A-Shell crash. Note that for ATE/ATSD, the update may be required on both sides in order to close the loophole. |
1194.2.2 |
ATE/A-Shell Windows input buffering refinement: There was effectively a limit of 3K on the amount of input data that could be buffered by ATE before it was processed. This was interfering with some commands (both ATE when the server is Windows, and in local A-Shell/Windows) that may have needed to return more than 3K at a time. (Retrieving clipboard data with MX_CLIPBOARD was an example.) The relevant buffers are now auto-expanded. |
1194.2.3 |
ATE command timeout refinement: the timeout on ATE commands now auto-extends itself if data is still being transferred. This resolves a problem with premature timeout when the data is taking longer than expected to be transferred from the client, but it is still coming. |
1194.1 |
COMIO.SBR bug fix: Recent changes (see 1193 below) introduced a bug in which opcode 4 (check for data) was waiting indefinitely (if no data was available) when the timeout was set to 0. This makes sense for the read and write operations, but not for the check operation. It now behaves as expected. |
1194.0 |
XTREE enhancement: The meaning of the XTR'USRCFG flag value 2 (previously named XTUCFG_SRTORD) has been changed to separate xtr'columnactive from the xtr'sortorder() and xtr'columnsort() information. This flag value (2) has been renamed (in xtree.def) to XTUCFG_COLSRT and now saves and restores only the xtr'sortorder() and xtr'columnsort() values. A new flag, XTUCFG_COLACT (value = &h0010) has been defined to save and restore the active column. To minimize the effect on existing programs, the old symbol, XTUCFG_SRTORD, has been redefined to &h0012, combining the two flag bits so as to preserve the old behavior. (So as long as you recompile your programs prior to installing this update, there will be no change at all.) If you don't recompile, any XTREEs using the XTUCFG_SRTORD flag will no longer save and restore the user's active column. (But this effect is probably too subtle for most people to even notice.) See the updated XTREE.DEF (edit 125) for the updated symbol definitions. |
