1169.9.1 |
Experimental AUI_CONTROL feature: setting the &h020000 bit in the CTYPE2 parameter of a MBF_STATIC control will cause the control to display a "button-like" border when the mouse is over it (i.e. hot tracking). This could be useful with MBF_STATIC controls that have click actions, but the implementation is likely to change, so don't do more than experiment with this. |
1169.9.2 |
XPUTARG / Dynamic String bug fix: XPUTARG was failing to clear the target variable (i.e. the calling param) when the source variable (the one being returned or "put") was an uninitialized dynamic string. Such stings have a size of 0, causing the transfer routine to transfer 0 bytes, which could have resulted in the calling routine mistakenly interpreting the parameter as having been returned from the last SBX or func/proc call rather than from the previous value of that parameter. |
1169.8 |
AUI_MENU bug fix: automatic deletion of child menu items was not working when a top-level parent menu with no itemid was deleted. |
1169.7.1 |
Compiler enhancement: instances of named structures can now be overlaid. For example: MAP1 REC,X,64 MAP1 CUS,ST_CUS,@REC MAP1 VEN,ST_VEN,@REC This was always possible with unnamed structures, so the technique is not new. Put previously, the compiler would have complained when used with named structures as in the example above. |
1169.7.2 |
EVENTWAIT bug fix: the fix in 1166.6 relating to EVW_NOFOCUS was causing the DEL key to no longer exit with exitcode -47. |
1169.6.1 |
GUI display fix: the background of static icons within a TAB control was displaying in black instead of transparent. |
1169.6.2 |
Static text controls with the FGC (foreground color) set to an RGB value and the BGC value set to -2 were sometimes getting an unexpected background color. |
1169.5.1 |
INFLD dynamic variable fix: when using a dynamic ENTRY variable, MAXCHARS was being effectively limited to the larger of XMAX and the existing entry variable contents. (Generally noticed as horizontal scrolling not working.) |
1169.5.2 |
Windows printing bug fix: the DELETE switch was not being obeyed in one particular set of circumstances involving APEX and ATE. |
1169.5.3 |
XTREE bug fix: Close a loophole in which ANSWER was being returned > 0 in the case where XTF_NOSEL was set (i.e. display only), but the incoming XTR'XROW field was > 0. This wasn't exactly a bug, but it started happening in 1169.0, and caused some applications to misinterpret the ANSWER>0 as indicating a selection operation. |
1169.5.4 |
INPUT bug fix: regular (non CSV) INPUT statements were failing to stop at the comma delimiters when the preceding field was quoted. (Problem introduced between 1163.0 and 1164.0 in the process of fixing INPUT CSV.) |
1169.4 |
Windows printing bug fix: close another loophole causing A-Shell to crash when the printer specified in the DEVICE= statement doesn't exist. (This problem introduced in 1169.2 while fixing a similar problem.) |
1169.3 |
Beveling bug fix: enabling 'beveling' and standard line drawing characters was leading to visual chaos, at best. Why anyone would want both is beyond the scope of this discussion, but if both options are enabled, you now get something more visually pleasing (similar to a double line with shading). |
1169.2.1 |
Windows printing bug fix: close a loophole leading to an infinite loop when the last user printer no longer exists and other conditions met. |
1169.2.2 |
Windows printing bug fix: in some cases, printing to the PROMPT: device was bypassing the print dialog and printing directly to the last used |
1169.2.3 |
Windows printing refinement: When attempting to match the requested printer from the printer init DEVICE statement against the available printers, the function which scanned the available printers was actually trying to open each one, which can lead to long delays in cases where printers are technically available, but unresponsive (or very slow to respond). To avoid this, we now use an alternate scan that only checks the local registry and thus is fast, but which can only compare printer names, not ports. (Since 99% of the time, the printer is identified by name rather than port, this limitation should not pose a significant problem. And in any case, if we fail to achieve a match on printer names, we revert to the previous method.) |
1169.1.1 |
VUE bug fix: A source line greater than 2022 characters containing TABs would crash VUE when you moved the cursor off the line. |
1169.1.2 |
SYSTAT.LIT 3.0(161) enhancement: new /H switch displays available disk space in "human-readable" units (GB or MB) rather than 'blocks'. Also, even without /H, the display format is automatically widened, but only if necessary, to prevent numeric overflow of the available disk blocks (more than 999,999,999 blocks). |
1169.1.3 |
DIR.LIT 3.0(148) bug fix: file names incompatible with AMOS file.ext format (e.g. with more than one extension) were being omitted from the output when the output was being sent to a file, even if /NA was specified. (This is normal when /NA is not specified). The problem only occurred when /NA was at the end of the wildcard list (rather than immediately following 'DIR'. (DIR/NA out.list=*.* was ok, but DIR out.lst=*.*/NA was not.) |
1160.0.1 |
XTREE bug fix: The patch in 1168.7 to support ANSWER > 32K had the side effect of returning ANSWER=1 (instead of 0) after an XTREE display using XTF_NOSEL. This was causing some applications to misinterpret the returned ANSWER value, as if the user had selected it, generally leading to chaos. Now fixed. |
1160.0.2 |
XTREE refinement: Displaying a multi-level tree with one or more levels collapsed was sometimes causing a "flash" as the expanded rows were first displayed and then collapsed. |
1160.0.3 |
XTREE bug fix: Optimization logic in 1166.3 was in some cases leading to an infinite loop on the initial load of a tree. |
