1372.7.1 |
Fix missing delimiter in control dump CSV header (from adding tabstop in 6.1.1368) |
1372.7.2 |
Fix problem with failure to load the most user/profile specific copy of the settings (i.e. the same ones that are saved by default). Introduced 1371.0 |
1372.7.3 |
Fix problems with control centering logic when parent is a static panel instead of a real window or dialog. |
1372.6.1 |
PCKLST bug fix: headers in simple-multi-column (non-COLDFX) mode were using the first line of data rather than the intended headers. |
1372.6.2 |
APEX bug fix: various options passed in to APEX, such as orientation, were not actually being recognized. Problem introduced in the big UNICODE shakeup between 1365 and 1370. |
1372.5 |
AUI_CONTROL bug fix: static images with one of the centering options were failing to get re-centered after resizing the window. |
1372.4.1 |
AUI_CONTROL bug fix: MBF_AUTOGROW controls were not getting resized properly when the window was resized. |
1372.4.2 |
MX_WINSETTINGS refinement: loading a new .ash file no longer triggers a resize operation unless something which affects sizing has changed. |
1372.4.3 |
AUI_CONTROL bug fix: resizing was causing some static images to act as if they had lost the MBF_NODISTORT option. |
1372.3 |
Static text background color bug fix: When dialogs or windows are stacked, in some cases static text controls created with bgc = -2 were picking up a bogus background color from a control in an underlying window. |
1372.2 |
MX_SHELLEX refinement: local mode (clisvr = "S" or "L") now supports the waitflag options and the exitstatus parameter. Previously, these only worked in the normal/default (client) mode where the operation is forwarded to ATE via the AG_SHLEXEC command. Also, both modes now support shell commands that require COM initialization. |
1372.1 |
INPUT statement bug fix: input lines longer than 32K were causing an overflow condition with unpredictable results. |
1372.0.1 |
Implement Named XCALL Parameters. |
1372.0.2 |
INFLD Enhancement: new type code "|&" works like a "smart" version of "&", re-enabling protected mode on exit only if it was previously enabled. The "&" feature always re-enables protected mode, which was the way it worked historically under AMOS. |
1372.0.3 |
MX_NOBUF, MX_FLUSHBUF, MX_FLSET bug fix: if the specified file channel was not open, it was failing to update the STATUS parameter. This would only be a problem if the calling program was re-using a previously-set variable, in which case it might be fooled into thinking that the specified file was open when it was not. The workaround—to avoid the problem without updating A-Shell—is to just set STATUS=0 before the XCALL MIAMEX,... |
