1329.4.1 |
Fix SIGSEGV issue related to interaction between SBX calls, USRMEM memory management, and the new call stack buffer tracing. |
1329.4.2 |
Fix failure to properly log a SIGSEGV error when it occurred between programs. |
1329.3 |
.ARGCNT refinement: The current .ARGCNT value (# of arguments passed to the current subroutine, function or procedure) is no longer wiped out by calls to functions or procedures. This eliminates the need to copy it to a local variable immediately upon entrance into a routine. Patch migrated from 6.0.1262.4 |
1329.2 |
XTREE/ATE bug fixes: clean up server-side memory leaks caused by deleting XTREEs implicitly (via TAB(-1,0) or by deleting the parent) rather than by explicit XTROP_DELETE calls. |
1329.1 |
Compiler edit 621 fixes an code generation bug (causing a runtime error when launching the program) related to a structure definition containing initial values but which is never used to instantiate a variable. |
1329.0.1 |
The auto-maximize-dialog global option { SBR=AUTO_DLG_MAX } now works on multi-monitor systems. Previously it only worked on single monitor systems. In the multi-monitor case, it operates relative to the monitor over which the center of the dialog (in its original coordinates) appears. |
1329.0.2 |
New MIAMEX function MX_SETERR (182) triggers a BASIC error. |
1329.0.3 |
New ERR(7) function reports the location of the last error within the current stack frame/scope. In contrast, ERR(8) reports the location of the original error. The two would differ if the error occurred within a function or procedure and was allowed to percolate up to a higher level, where ERR(7) would indicate the line that called the function or procedure. Note: ERR(8) was changed in 6.1.1325 to indicate the location in the current stack frame; ERR(7) now serves that purpose and ERR(8) goes back to its historic meaning. |
1329.0.4 |
(ATE/PolyShell) PolyShell was being inadvertently disabled by an XCALL AMOS operation. The problem was introduced in 6.1.1315 when the client-side hot-key-between-sessions feature was introduced. |
1329.0.5 |
(UNIX/PolyShell) PolyShell was being inadvertently reactivated within an XCALL AMOS session, which opened the possibility of hanging the job if the hot key was used before the AMOS session returned. It is now disabled to prevent this, as it is during a HOSTEX, and re-enabled on return to the main process. |
1329.0.6 |
TABX refinement: reinstate automatic BGC transparency for text items on TABX controls if the requested BGC < 64. |
1329.0.7 |
Compiler edit 620 fixes bug relating to instances of structures within structures which included initial values. |
1329.0.8 |
GUI bug fix: the local auxiliary file lookup was not scanning the CACHE and ATECACHE directories when then filespec contained an undefined (ersatz) device. Problem was introduced in 6.1.1319 (during fix to a different problem with translated filespecs containing undefined ersatz devices). |
