970.5.1 |
Fix: The enhancement of 970.1.5 to detect access to a DIMX'd var before the DIMX was actually executed had the undesirable side effect of applying to any unmapped array. |
970.4.1 |
VIC32 library errors are now reported to the debug message window, opening it if necessary. This helps debug a problem which has intensified recently when certain control types with images started using VIC32.DLL to load the image, rather than letting the control creation API do it. Because of this increased reliance on VIC32.DLL, we are now including it with ATE and ASHW32. |
970.3.1 |
A new function ++INCLUDE'ONCE cancels the ++INCLUDE operation if a file with the same name and extension has already been included. |
970.3.2 |
Fix problem with use of system functions in the argument list of user-defined procedures. |
970.3.3 |
TRACE.PRINT / PAUSE.PRINT no longer tries to replace % characters with parameter substitutions unless the string being printed starts with $ (i.e. $# or $T). In that case, you should avoid trying to output string messages certain % character sequences such as %s, %d, %x as the internal string formatter will replace them with arguments that probably aren't defined and will end up as numeric garbage. |
970.2.1 |
Fix: the test for invalid ANSARY (see item 6, 970.1 below) was falsely reporting a problem when running with older A-Shell/UNIX. |
970.1.1 |
INCLUDE'ONCE now supports a flexible index. |
970.1.2 |
Further improvement to the control dump to provide more human-readable class names and to distinguish between variations of the same class (like Date or Time, vs. DATETIME). |
970.1.3 |
Fix the FONTWIDTH and FONTHEIGHT printer initialization parameters that were broken in in 958.1. |
970.1.4 |
Fix: FOR/NEXT loops were generating compiler syntax errors within functions. |
970.1.5 |
Attempts to access a DIMX variable before the DIMX statement is actually executed are now flagged with error 30 (subscript out of range.) Previously, no error was triggered, with unpredictable results. (Note that the compiler "defines" variables when it sees a MAP or DIMX statement during compilation, regardless of whether the statement is in the execution flow of control. But in the case of DIMX, the defined variable is just a placeholder of minimal size, until the DIMX statement is executed at runtime.) |
970.0.1 |
Implement Extended MAP Statements for fine tuning of scope of variables (MAP or DIMX) in the context of functions and ++includes. |
970.0.2 |
Slight modification to control dump - Class column now contains more friendly class names, and a new column has been added for the real class names. |
970.0.3 |
The XTREE backslash \ character now marks the start of hidden text within a column in array mode, just as it does in file mode. Note that to treat backslash as a normal character, you need to add the \ code to a column definition (any column will do). (WARNING: This may break existing XTREEs that contain backslashes in the array data since previously the \ column code was not necessary for arrays; talk to Herman if you don't like this, or just add \ to your column definitions.) |
970.0.4 |
TAB(-1,20) (read character at cursor address) is now supported under Windows and ATSD. |
