1191.6 |
XDATE.SBR bug fix: An input date missing the first field (e.g. '/12/10') was resulting in a bogus return date. Now it is flagged as invalid. |
1191.5.1 |
INFLD bug fix: rubout in auto-complete mode was not exiting for refresh of the list data if the field contents matched the first item in the list. |
1191.5.2 |
ATE function key handling bug fix: use of function keys (and GUI objects with VK_F# clickstrings) was in some cases not resulting in the expected (exitcode) result. One example: INFLD with auto-complete list data showing. Note: problem did not affect clickable objects which used the "extended function key coding", i.e. "VK_xF###" |
1191.4.1 |
MX_FINDNEXT refinement: test for common mistake of including the first argument from the MX_FINDFIRST call. |
1191.4.2 |
SORTIT refinement: minor improvement in the parameter error reporting. |
1191.3.1 |
ISMUTL.LIT 1.3(134) now allows 0 as the record size, needed for "pure" indexes. Previously, such an index could only be created via ALLOCATE'INDEXED. |
1191.3.2 |
ISAM-A bug fix/enhancement: "Pure" indexes (see 5.1.1121) were not supporting the GET'LOCKED statement, which made it difficult to use UPDATE'RECORD or DELETE'RECORD to update index entries. See the sample program PURIDX.BP in the EXLIB [908,33] account for an example. |
1191.3.3 |
APEX bug fix: If the native print file path (including the APEX directory) contained a "-", the printfile name got truncated there. (This wasn't critical, except when it occurred in a directory name.) |
1191.3.4 |
XTREE XTF2_CSV fix/refinement: XTF2_CSV mode now supports XTF_COLDFX case where only pseudo-columns are defined (i.e. for colors, fonts, etc) in the COLDEF string. If no real columns are defined in the COLDEF, it then reverts to automatic column definition mode (getting the column info from the next line of the CSV), as if XTF_COLDFX had not been set (i.e. as if no COLDEF was used at all). This is now consistent with the existing documentation. |
1191.3.5 |
XTREE refinement: Clicking out of cell editing by clicking on a editable cell of another tree was previously sometimes requiring multiple clicks before it would enter cell editing mode in the target tree. |
1191.2.1 |
AUI_CONTROL bug fix: CTLOP_INFO wasn't returning the dll name for icon buttons (e.g. resname::dllname); introduced in 1190.5. |
1191.2.2 |
Array handling runtime bug fix: Any access to an unmapped array was generating a subscript out of range or out of memory error. Problem introduced in 1190.0. |
1191.2.3 |
Compiler bug fix (AIX only): A bad link module was resulting in segmentation fault errors during compilation. (New compiler edit: 461) |
1191.1.1 |
XTREE bug fix: cursor was being left in hourglass mode on display only trees. |
1191.1.2 |
XTREE refinement: when exiting from the tree is allowed with up arrow or down arrow, it now requires a minimum of 1/3 second since the last arrow key to allow the exit. This eliminates the problem of holding down the arrow key to scroll up/down and then finding yourself out of the tree and several fields away due to the up/down arrow exiting and then being interpreted by other controls as next/previous field. |
1191.1.3 |
Fix: SBRC.SBR op 1 was returning both P and PN fields set to the P value. |
1191.0.1 |
Add subroutine MX_IATIMEOUT to query and set the inactivity timeout period. |
1191.0.1 |
Minor refinement in the expansion heuristics used by DIMX with AUTO_EXTEND. When the array needs to be expanded, it is now expanded by a minimum of 150% of the previous array size, or 110% of the size required for the assignment triggering the expansion. But, this is then limited to no more than 128K beyond what would be required for the current assignment. Also, a 128K grace or overage is now added to the MALLOCLIMIT value, to prevent the possibility of the expansion failing because of these heuristics. |
1191.0.1 |
XTREE / ATE server-side bug fix: Close a loophole in the optimizer that was resulting in a failure to load a tree in an obscure multi-tree case where two trees had identical data. |
