1426.9 |
XTREE refinement: null fields with the cformat P option were resulting in garbage being loaded into those fields. |
1426.8 |
XTREE bug fix: date/time sorting (cformat D and h) was not working. It was broken in 6.1.1365 during during the unicode conversion. |
1426.7 |
XTREE bug fix: close loophole responsible for intermittent bogus "Editable column count" error messages. |
1426.6 |
Fix truncation problem in standard TAB control if the label definition string (ctext) between 200 and 400 characters; Was corrupting the exitcode for the final tab. (Retrofitted from 6.3.1512.2) |
1426.5.1 |
Parameter passing bug fix: a passed floating point variable was failing to be converted properly to a received string variable if the receivng string variable length matched the passed floating point variable length. For example, passing an F6 to an S6 or an F8 to an S8 was not giving the expected result. |
1426.5.2 |
XTREE/ATE bug fix: the answer array wasn't getting reprocessed in XTROP_REPLACE mode when the data array was updated and row optimization was resulting in only the updated rows being transmitted to the client. |
1426.5.3 |
Refinement to XTREE handling of optional editable dates (cformat=DE, InfDef=DO). Now, when the date-valid checkbox is unchecked, the date displayed will be blanked out. Previously, it was grayed out, but the difference wasn't enough to avoid confusion. Retrofitted from 6.3.1510.1. |
1426.5.4 |
ATE bug fix: the AutoMouse option saved in the configuration settings was being overridden by the default settings. |
1426.4 |
Message boxes are no longer suppressed due to the -zi switch if the window has already been made visible by other means first. |
1426.3 |
Further fix to STRTOK (see 1426.0) to ensure that the RDELIM parameter returns the final record delimiter character when the final field is terminated by only a record delimiter (rather than by field and record delimeter). Normally this would not be an issue, since programs that use STRTOK to process multiple records would have to deal with possibility of a totally empty record at the end (which will always return "" in RDELIM). But for programs parsing just a single record with an unknown number of fields and expecting the final record delimiter to be returned in RDELIM after the final field, the prior behavior may have caused the application to report an error condition. |
1426.2 |
Minor refinements to close loopholes in which interactions between startup errors and error messaging/logging routines could lead to lockup ofthe entire system. |
1426.1.1 |
File hook bug fix: close a memory corruption loophole. The loophole was small but was most likely to be exposed when a single program opened, closed and hooked many files repeatedly. Symptom was typically a GPF or segmentation fault. |
1426.1.2 |
(LINUX) Minor adjustment to terminal drivers to avoid a weakness in an optimized version of some string handling library calls introduced in -el6. No problems had been observed or reported though; the adjustment just reduces uncertainty in the library implementations. |
1426.0.1 |
MX_GETOFD refinement: minimum number of parameters has been reduced from five to two, allowing you to call it with just xcall MIAMEX, MX_GETOFD, PATH$ |
1426.0.2 |
(LINUX) LOKUTL.LIT 3.0(114) bug fix: previously wasn't handling inodes greater than 64K. |
1426.0.3 |
Bug fix: passing an element of an unmapped array to a function or procedure was corrupting the GOSUB/RETURN stack if the array had not yet been seen by the runtime system and the call occurred within a traditional GOSUB routine. Symptom was a segmentation fault or GPF. Note: this bug fix should not be viewed as encouragement for such use of unmapped arrays. MicroSabio highly recommends mapping all your variables so that the compiler can help you spot typos that can lead to nasty errors. |
1426.0.4 |
|
1426.0.5 |
WHI Catalog Update: Linux -el5-tw version now contains the 48.5.1.2 version of the SDK, used by MPSCOM.SBR. Previous version was 48.1.4.1. |
