1715.12.1 |
Compiler edit 988: minor refinements to the LSX file structure to ensure that the LSX compilation is fully independent of the environment in which it was created. |
|
---|---|---|
1715.12.2 |
Fix |
Compiler edit 989: close a loophole introduced in edit 984 resulting in the corruption of some function calls and XCALLs, primarily in the CentOS environment. |
1715.12.3 |
New |
VERSYS.LIT 3.1(109) enhancement: display now includes many additional details about the specified program, include memory requirements and the existence of embedded resources such as dynamic functions and embedded structure definitions. |
1715.12.4 |
New |
COPY.LIT / MOVE.LIT 3.4(146) enhancement: add /MAXDAYS:## and /MAXSECS:## switches to allow selective targeting of files changed recently. |
1715.11.1 |
DO.LIT / MDO.LIT 2.1(126) enhancement: special colon commands (e.g. :K) can now be indented. Previously they needed to be in column one. This may be a minor detail but can make all the difference in debugging complex DO files with many levels of nested IF / ENDIF clauses. |
|
1715.11.2
|
Fix |
Compiler edit 987: Fix problem with ++INCLUDE'IF'EXISTS when compiling an LSX file in a different environment than where the LSX file was originally created. If the existence at the time the LSX was created didn't agree with the existence when compiling the LSX, the ++include nesting levels would get out of sync with the original, possibly leading to bogus compilation errors. |
1715.10 |
Fix |
Compiler edit 986: The first unmapped variable, if numeric, was failing to finalize the definition of last mapped variable, causing it to behave in certain expressions as if it had the default size for its type. Problem was introduced in one of the early 6.5 versions. |
1715.9.1 |
Fix |
Compiler edit 985: DEFTYPEs associated with structure members were not being saved or retrieved by the MX_DYNSTRUCT operations. The native type,size info was still correct, but applications relyon on the DEFTYPEs were out of luck. Bug was introduced in 6.5.1711. |
1715.9.2 |
Fix |
MX_DYNSTRUCT: close a small window of opportuntity for an overflow condition to result in corrupted dynamic structure definition, most likely crashing the application. |
1715.9.3 |
Fix |
Fix AUI_CONTROL and the MBF2_DLGSTATE refinement in 6.5.1715.8. In some cases when reverting back to the original design coordinates, instead of the last saved coordinates, it was confusing the AUI coordinates with pixels, resulting it wildly unexpected dialog sizes. |
1715.8.1 |
Compiler edit 984: tighten the syntax checking on named parameter lists (both XCALL and function/procedure) to require that scalar parameters are passed scalar values and array (byref) arguments are passed array (byref) values. |
|
1715.8.2 |
AUI_CONTROL refinement to MBF2_DLGSTATE feature: saved coordinates are now ignored—i.e. reset back to the design coordinates—if the design coordinates have changed since the dialog was last saved, or if the dialog no longer fits entirely within the virtual desktop space. |
|
1715.8.3 |
XTREE refinement to the XTR'USRCFG feature: saved column information is now ignored / reset if the number of columns in the tree has changed since the last time the tree was displayed. This is purely a convenience to aide programmers who forget to change the TreeID when adding or deleting columns, which would otherwise lead to confusion and wasted time as the saved column widths and order would be applied to the wrong columns. |
|
1715.7.1 |
Fix |
Compiler edit 983: further refinement to edit 982 to eliminate spurious complaint about XCALL array parameters with spaces within the parentheses, e.g. XCALL MYSBX, ARY( 1 ), ... |
1715.7.2 |
Fix |
XTREE: restore operation of the multi-checkbox toggle feature (using SHIFT-CLICK) which was broken in 1715.0 by the new local validation logic. Note that as before, validation logic is only executed on individual clicks, not on multi-checkbox toggles. |
1715.6 |
Fix |
Compiler edit 982: replacement for edit 981 (which was recalled). |
1715.5 |
Fix |
Compiler edit 981: extend the fix in compiler edit 978 to apply to XCALL named parameters (defined with DEFXCALL). As in the prior fix, array parameters now require a pair of empty parentheses in the formal name, for example: defxcall MYSBX, MYARY() ... dimx ARY(0), ST_TEST, auto_extend ... xcall MYSBX, MYARY()=ARY()
Previously the () was not recognized in the DEFXCALL, forcing you to refer to the named array as if it was a scalar, creating a variety of possibilities for ambiguity and confusion. Note that as with the earlier fix, the compiler may now report errors in programs that previously compiled and ran ok. |
1715.4.1 |
Fix |
XTREE: further minor fixes related to cell editing validation. |
1715.4.2 |
Fix |
|
1715.3 |
Fix |
XTREE: several minor fixes related to cell editing validation, for bugs introduced with the local validation feature in 1715.0. |
1715.2 |
Fix |
XTREE: several minor fixes related to cell editing validation. |
1715.1 |
|
Minor enhancement to GUI traces related to MBF2_DLGSTATE. |
1715.0 |
New |
XTREE enhancement: support for local (or client-side) validation of editable cells via an internal call from XTREE to a specified XTREE Local Validation SBX. |