1198.4 |
GUI click timing adjustment: refine the change in 1198.2 to shorten the time window for buttons and static control clicks to allow one new click event for the same button every 0.5 seconds. |
1198.3 |
XTREE refinement: New advanced column definition option ColOptRows allows better control of column width. |
1198.2.1 |
Compiler (475) bug fix: In /x:1 or /x:2 mode, it was failing to detect and report the following two kinds of errors: FOR I=1 TO 2 PRINT I:NEXT I ! (missing: ) FOR I = 1 TO 2 ... NEXT J ! (mismatch FOR/NEXT var) |
1198.2.2 |
GUI bug fix: close a timing loophole which was causing the first click on a control to sometimes be ignored, if coming within 1.5 seconds of the last click on some other control. |
1198.2.1 |
ATE bug fix: close a loophole that was intermittently allowing garbage to be transmitted to the server at the end of the CTLOP_INFO operation. Typically this caused no problems, but occasionally the garbage contained control characters (like Ctrl+C) that would abort the server program. The problem has been around for a long time, but happened so rarely that it was just now noticed. (Unrelated to any of the other changes in 1198.) |
1198.0.1 |
This release consolidates various ATE/XTREE related performance optimizations introduced since 1197.0, which require both sides (server and client) to be at least at this level to take advantage of. (If either side is lower, then the optimization is not activated.) |
1198.0.2 |
Windows GDI printing bug fix: The %# (total pages) macro was being fooled by a trailing FF character into adding an extra page to the total, even in cases where the FF would have been removed by subsequent processing. This was mainly noticeable in AUXLOC: printing, but possibly other scenarios as |
1198.0.3 |
(Linux version) TLS support reinstated (after being inadvertently turned off for the last few versions). |
1198.0.4 |
XTREE enhancement: A new flag, XTF2_NORESPONSE, may be specified to eliminate the return of any response information for a particular XTREE call. This is purely of interest in the ATE environment as a performance enhancement (since the return of response information causes the application to have to wait for the network turnaround time, which is small but adds up.) In order to be effective, it must be used along with the XTF_NOSEL flag (which is used when you want to display some data without waiting for a user section or editing action). Warning: don't use it along with XTR'CTLNO = -1, since in that case you won't get back the updated tree control number, which could make it difficult to reference the tree on subsequent calls. |
