1424.3 |
Prevent accidental mouse drag problem in Month Calendar control by forcing an automatic mouse-up event. Some users were reporting that they would click on a date to select it, but then when they moved the mouse the date would change as the mouse moved over other dates. |
1424.2.1 |
DIR.LIT 3.3(158): remove incorrect /MDATE, /MTIME switches from the help display. The correct switches are /UDATE and /UTIME. |
1424.2.2 |
Runtime nested array expression evaluator bug fix: using an ordered map expression as a subscript to another array was resulting in a bogus subscript out of range error, even when the value of the ordered map expression was non-zero. For example: map1 array(10),f $roomno("smith") = "5" array($roomno("smith")) += 1 This should be—and now is—legal, since even though "5" is a string, it auto-converts to a number when used in a context that requires a number, as is the case in for an ordinary array subscript. Same fix in 6.3.1507.0. |
1424.1.1 |
Windows UI bug fix: Alt+Enter—used to toggle between max and normal main window state—wasn't respecting the -mx command line switch, which removes the min/max/norm buttons from the main window, presumably to prevent the user from changing the window state. |
1424.1.2 |
ISMBLD.LIT 2.1(142) bug fix: the current logged-in device was being stored in the IDX as the IDA device when the /L:# or /B:# switch was being used. The IDA device should have been left blank except in the case an explicit device specification appears on the ISMBLD command line. |
1424.0 |
Add new MIAMEX function MX_MALLOCLIMIT (185) to get/set the MALLOCLIMIT: xcall MIAMEX,MX_MALLOCLIMIT,op,limit where: op [in] (num) is 0 to get the limit and 1 to set it limit [in/out] (b,4 or f) returns the current limit (op=0) or supplies the new limit (op=1). Units are bytes—not kilo-, mega-, or giga-bytes. Maximum practical limit is 2GB-1 (2147483647). |
