1687.6
|
Fix
|
XTREE: Enabling export-related SBR options in the miame.ini was in come cases causing XTREE to crash when the context menu displayed.
|
1687.5
|
|
Minor XTREE tracing refinements.
|
1687.4
|
Fix
|
Close loophole in 1687.3 bug fix which could result in LOKSER queue overflow.
|
1687.3
|
Fix
|
RELEASE'RECORD #CH (without specifying a record number) was, in rare cases, triggering an ISAMA EBADF error. The problem was introduced in 6.5.1684.0, and occurred only when the current record number was 0, which normally only occurs after opening an empty file.
|
1687.2
|
Fix
|
MX_OSVER was returning the ATE OS release and platform fields in the ATE OS version and ATE release fields, respectively, when the OS version is empty, as it currently is for Windows 10.
|
1687.1
|
Fix
|
XTREE: the $XTRCSV and $XTRCSV2XL were failing to output any data. The problem was introduced in 1683 when the $XTRCSV2XLSX version with color support was added.
|
1687.0.1
|
New
|
Language enhancments in compiler edit 935: Add new dot variables
.MILLITIME returns number of milliseconds since midnight
.MICROTIME returns number of microseconds since midnight
Note that due to quirks of the system scheduling clocks on different platforms, the resolution of the .MICROTIME results may not be as granular as one might expect.
|
1687.0.2
|
Fix
|
Compiler edit 935: a missing closing end of a function parameter list wasn't always being flagged as a syntax error. It was compiling as if the closing parenthesis had been there.
|
1687.0.3
|
Fix
|
Several dot functions which take an argument, such as .RECSIZ(ch), .FSTAT(ch), .LINENO(ch), etc. were not working properly in multi-part expressions except when they were the first argument. For example:
IF .FSTAT(CH) = -3 THEN ... ! worked correctly
IF -3 = .FSTAT(CH) THEN ... ! was comparing -3 to CH, not .FSTAT(CH)
|
