1662.6 |
Fix |
XTREE: close a loophole in which clicking on an editable cell in an tree that isn't currently active was sometimes resulting in the wrong cell getting the focus, possibly even with that cell's data then getting written to the originally targeted cell. |
1662.5.2 |
Fix |
(ATE client) XTREE: Close a loophole in which image resources might be prematurely deleted during a XTROP_REPLACE operation using the ATE row optimization protocol (which eliminates transferring and updating rows from the server to the client that haven't changed.) |
1662.5.1 |
(Linux) Refinement: AXL library module (libxl.so) now supports up to version 3.8.5; previous limit was 3.7.2. Numerous minor improvements and bug fixes, particularly in the area of XLSX support. |
|
1662.4.4 |
Fix |
Further refinement to TotalLines, so that setting TotalLines to a non-zero value and then later removing the TotalLines clause from the coldef during a replace operation now always clears the setting. |
1662.4.3 |
Fix |
XTREE: certain clicks on inactive trees were failing to send the activation string, resulting in the control being given the focus without the application realizing it. |
1662.4.2 |
Fix |
Hex conversion (Linux only): conversions from hex format strings, e.g. val("&h00aaf18c") were sometimes producing wildly incorrect results. |
1662.4.1 |
DIR.LIT 3.4(169) enhancement: support for new switches /LT (descending by update date, similar to native UNIX ls -lt) and /P (pause after each page of output). |
|
1662.3 |
Fix |
XTREE: calling XTREE with TotalLines=N (N>0) and later calling the same tree using XTROP_REPLACE but with TotalLines=0 was effectively leaving the TotalLines values set to 1 instead of 0. Note that the XTF_TOTALS flag, while still supported, is now deprecated and has no other purpose than to set the default value of the TotalLines option to 1. |
1662.2.3 |
Tracing refinement: increase maximum size of each generation of the ashlog log file from 3MB (Windows) or 5MB (Unix) to 10MB. |
|
1662.2.2 |
Fix |
Compiler edit 909: compiler was failing to recognize the new LSX headers, causing total failure to be able to recompile LSX files. |
1662.2.1 |
Fix |
AUI_CONTROL bug fix: the MBST_CENTER option was not working properly when the parent object was in negative coordinate space—i.e. to the left of or above the primary monitor. |
1662.1.1 |
Fix |
Memory corruption bug fix: close a loophole that was allowing corruption in rare cases on return from an SBX if the SBX moved a shared memory block. |
1662.0.6 |
Fix |
Compiler bug fix (edit 908) - fix failure to allow IFE() and IFE$() functions within relative expressions, e.g. IF IFE$(A$,B$) = C$ ... |
1662.0.5 |
Fix |
Close a potential GPF or segmentation fault loophole in the return from an AG_XFUNC or MX_AGWRAPPER operation. |
1662.0.4 |
New |
|
1662.0.3 |
New |
|
1662.0.2 |
New |
Modify relevant LITs to accommodate Long File Names in LIT Commands. |
1662.0.1 |
New |
Increase internal maximum filename.ext length for A-Shell-compatible files to 72 for the filename and 8 for the extension. Previously the limit was 10.3 for ambiguous contexts (where it wasn't otherwise obvious if the filespec was meant to be A-Shell-style or native-style), and 32.8 for MX_FSPEC conversion operations where the context was explicit. |
