1354.7.1 |
XTREE bug fix: Setting the XTR'TOPINDEX field wasn't having the desired effect for multi-level trees when XTR'EXPANDLEVEL was also in effect. Also, XTR'TOPINDEX now works when the tree is initially created (opcode XTROP_CREATE); previously it was always cleared on creation. |
1354.7.2 |
EVENTWAIT refinement: When the EVW_ACCEL flag is set, underlining of the hot keys is now forced on. Previously, and otherwise, it follows the Windows convention, showing them if the last input event was a keyboard event and hiding them if it was a mouse event. |
1354.7.3 |
EVEWTWAIT bug fix: When the EVW_ACCEL flag is set, lower case characters a-j (without pressing the ALT key) were not working as expected. |
1354.6.1 |
*IMPORTANT* ISAM 1.x bug fix: The key deletion routine was failing to unlink empty top-level blocks created by deletions in a top-heavy index, and this was causing subsequent operations on the index to corrupt it. The problem has potentially affected all ISAM files with more than 3 IDX levels or larger than 512 byte IDX blocks, and was expanded to all files starting in 6.1.1344 when the traditional ISAM 1.0 implementation was completely replaced by ISAM 1.1. However, in no case did it affect files with only a single top-level IDX block, and even then it generally required a lot of consecutive deletions, which is probably why it has taken so long to surface. With this patch, existing non-corrupt files do not need to be rebuilt, although you may want to check for the existence of top-heavy IDX files (those with more than one top level block, which ISMDMP/V will display) and consider dumping them (checking to see that the number of records dumped matches the number of records allocated according to the ISMDMP TTY: or DDT: option), and then rebuilding them (preferably taking advantage of the ISMBLD/A option) in order to optimize the structure. Files thus optimized would be compatible and safe to use with older A-Shell releases. |
1354.6.2 |
XTREE refinement: The range of values possible for XTR'ITEMLINES field has been extended on the low side from -6 to -8. Although -6 theoretically provides no extra leading, it turns out that when using the XTF_VARY flag, the rows are more tightly spaced than XTR'ITEMLINES = -6 (without XTF_VARY); XTR'ITEMLINES = -8 comes closer to the emulating the XTF_VARY spacing. |
1354.5 |
ISAM 1.x refinement: Index scanning logic can now deal with empty top-level index blocks, which could result from a bug in the key deletion logic. With this patch, such files can be dumped with ISMDMP and rebuilt using ISMBLD, but it doesn't fix the underlying problem in the delete routine. See notes above for 1354.6.1.. |
1354.4 |
XTREE bug fix: Under some circumstances, if a checkbox cell was toggled, subsequent clicks outside that cell would act as if they were still in the cell. (Problem was introduced in edit 1352.0) |
1354.3 |
Compiler bug fix (edit 640): Fix spurious compiler complaints about unmapped $$ variables and duplicate labels in FOREACH loops; the bug was introduced in edit 639. |
1354.2.1 |
Compiler bug fix (edit 639): REPEAT wasn't working correctly in FOREACH loops. The code generation was faulty, so the fix requires recompilation but does not require a runtime system update. |
1354.2.2 |
AUI_CONTROL bug fix: Static text controls with the right or center justification were being truncated to 150 characters of text. |
1354.2.3 |
ISAMPLUS bug fix (Linux): Versions of A-Shell compiled and running under RHEL/CentOS 6 were exhibiting index file corruption due to an overly enthusiastic optimization of the memcpy() routine which was affecting adjacent but non-overlapping regions. New version of the library (6.11n) works around the problem by using a different memory copy algorithm. Note: this problem was not known to have occurred in any standard A-Shell release but an update is recommended for anyone running newer Linux versions and ISAMPLUS. |
1354.2.4 |
INFLD refinement: When a combo box displays more characters than MAXCHRS and allows for non-matching items (by virtue of a * in the SETDEF list), replacing a matching item with a non-matching one now clears the remainder of the display field, avoiding some visual confusion about whether the item really was a match. |
1354.2.5 |
BASIC error trapping refinement: error description is now included along with the error # in the message logged to the ashlog.log and, if applicable, to the debug message dialog. |
1354.2.6 |
BASIC error trapping refinement: when running in local Windows mode, the debug message dialog will now only be displayed for BASIC errors if there is at least one dialog on the screen. Previously it was displayed if there had been any GUI controls previously created. |
1354.1.1 |
Numeric-to-string conversion bug fix: Previous patch (1354.0) resulted in unwanted scientific notation when the number of significant digits exceeded the SIGNIFICANCE setting. All numeric-to-string conversions except unformatted PRINT statements are now based on a significance factor of 11. |
1354.1.2 |
MBF2_STICKY refinements to support sticking dialogs—particularly caption-less dialogs—to the edges of a parent dialog or main window. |
1354.0.1 |
New BASIC statement CLEAR $ARY() removes all of the elements of the (associative) array without deleting the array itself. |
1354.0.2 |
New GDI print directive //RESETFONT restores original font. |
1354.0.3 |
APEX bug fix: In the type of report described above, scrolling backwards from the page with the explicit //SETFONT commands to a prior page which was using the default font was not properly resetting the original default font. APEX now effectively inserts the //RESETFONT command in to the preview document to deal with the situation. |
1354.0.4 |
DIR.LIT 3.3(152) new switch /1 eliminates the directory and size information from the output. When combined with the /NATIVE switch, it produces just a list of filenames (file.ext), similar to the UNIX ls -1 command. |
1354.0.5 |
ISAMPLUS library minor update, now version 6.11m: works around quirk in EFS which caused failure to open due to locking conflict to return error 20 (device error) instead of err 37 (file in use). |
1354.0.6 |
LDF-related bug fix: conversions from numeric to string which occur during parameter passing (SBX, function, and procedure) were not taking into account the LDF setting for the decimal point indicator. This was a problem in environments that use comma for the decimal point. |
1354.0.7 |
STR(x) was always formatting the string as if the SIGNIFICANCE was set to 11; it now uses the actual SIGNIFICANCE setting. |
1354.0.8 |
AUI_CONTROL bug fix: further refinement to the CTLOP_DEL operation (see 1353.8) to properly handle certain hierarchies of Tab, dialog, static frames and their children. |
