1131.9.1 |
XTREE bug fix: Close GPF loophole when COLDEF param more than 1024 bytes. |
1131.9.2 |
XTREE bug fix: The Dspmin= advanced COLDEF clause was persisting beyond the current tree, causing columns in subsequent trees to be affected (even un-hiding hidden columns in some cases). |
1131.9.3 |
XTREE bug fix: A problem in XTROP_PRINT was causing a sort of infinite loop. |
1131.8.1 |
XTREE Print/Preview Function bug fix: now prints more closely to how the columns are displayed. Previously, the columns were too wide, causing only the first couple of them to be displayed in the print/preview. |
1131.8.2 |
XTREE new COLDEF clause: Title=<title used in printing> The title string is currently only used as a page head and window title when using the XTREE print function. |
1131.7.1 |
Email.Type.4 bug fix: The Email.LogFile option was not supporting regular AMOS-style filespecs. The default remains OPR:SMTP.LOG |
1131.6.1 |
GDI printing bug fix: "%#" was not getting converted to the total # of pages if the file was not first previewed or pre-processed by APEX. |
1131.6.2 |
A spurious annoying warning message about not being able to find the .ash file has been eliminated. It occurred on new installations up until a user-private .ash file was first saved. |
1131.5.1 |
MX_WINSETTINGS now supports op 3 (see AG_WINSETTINGS in 1131.4 below). Also, both MX_WINSETTINGS and AG_WINSETTINGS now support a new field, AWS_CHARSET (20) to set and retrieve the current display character set. Valid choices are 0 for ANSI and 255 for OEM. Note that the character set is usually established in the MIAME.INI (default is OEM) with the FONT=fontname,charset command. Once set, changing fonts doesn't usually change the character set. |
1131.5.2 |
Settings file (.ash) enhancement: the character set is now saved and restored, overriding the character set established in the MIAME.INI. |
1131.5.3 |
Font selection refinement: selecting the new Vista mono-spaced font "Consolas" now automatically sets the character set to ANSI. (This is an exception to the behavior just noted above in which changing fonts doesn't usually affect the character set. The reasoning here is that Consolas is destined to become a popular font, yet is doesn't support OEM at all, which would result in some other font being selected in order to satisfy the OEM character set, most likely with horrible results. So in this case, we set ANSI automatically.) By the way, despite OEM being the default, ANSI is almost always a superior choice. |
1131.5.4 |
ATE printing refinement: When ATE receives a file to print via the AUXLOC: device, it stores the file in the My Documents\APEX directory, appending a -# suffix to the name to make it unique. (This way, if you reuse the same report file name, APEX will be able to keep unique copies for reprint/review purposes.) So, for example, if the application printed a file call "abcdef.prt", ATE might store it as "abcdef-3.prt". In the case of APEX, the file may then be converted to "abcdef-3.apf" (APEX performs some preprocessing on the file to facilitate paging operations.) Previously, there was no guarantee that the suffixes of those two files would be the same, which caused some complications for applications that try to either trace files through the printing process, or which need to send auxiliary files to be associated with specific print files by name. Now, ATE assigns unique suffixes in such a way that they do not conflict with any existing APEX apf files, and thus APEX does not have to reassign the suffix. |
1131.5.5 |
TAB(-10,AG_FTP) enhancement: you can now Assign PC Print File Name. |
1131.5.6 |
ATE printing refinement: A new virtual printer, "NULL", can be specified in order to get the normal file capture and assignment of unique name in the APEX holding directory, without actually printing. You can use this technique to reverse the order described above, sending the metadata file first and then the print file, in this case using the "-#" suffix on the print file itself (in order to make it match up with the previously sent metadata file). |
1131.4.1 |
INFLD GUI bug fix: Combo mode was not supporting SBR=INFLD_GUISELPOS properly, causing it to return EXITCODE=7 for left arrow in some cases, instead of EXITCODE=2. |
1131.4.2 |
File Save (settings) dialog refinement: The dialog was misleading in indicating that the settings were loaded from %APPDATA%\... (user settings) even when that file didn't exist and the settings were actually loaded from the shared %MIAME%\<profile>.ash or default.ash. |
1131.4.3 |
TAB(-10, AG_WINSETTINGS) enhancement: you may now load settings from a file. |
1131.4.4 |
TELNET.LIT 2.0(135) now uses TAB(-10,AG_WINSETTINGS) to reload the window settings after you select a connection profile, allowing the previously saved settings from that connection to be restored. Previously, the session saved settings were not being restored unless you used a desktop shortcut that explicitly specified the connection profile name (so it would bypass the dialog allowing you to select a connection.) |
1131.4.5 |
Compiler enhancement (edit 423): maximum number of levels of ++include nesting increased from 3 to 13. |
1131.4.6 |
XTREE bug fix: Clicking on certain empty areas within an inactive XTREE was giving it the focus but not sending the activation click string/exitcode. |
1131.3.1 |
Windows printing bug fix: FORMFEED=OFF was being ignored for passthrough mode. |
|
Windows command line processing bug fix: Under certain circumstances, a filespec appearing on the command line with an embedded "\n" was being confused with a new line, causing the filespec to be broken in two and some kind of confusing error message about a file not found to result. Also, ATE and default command lines were being truncated at 15 tokens. This has been increased to 31, to allow for very complex command lines. |
1131.1.1 |
TAB(-10,AG_FTPSYNC) now supports hash codes as a way of making sure whether the files are different or not. (If they are different, then the server version should be copied to the client.) Previously the decision was based only on the file size being different, or the server file date being newer than the pc file date. |
1131.1.2 |
ATSYNC.LIT 1.0(107) now supports hash codes as a way of making sure whether files are different or not. Also, it now works from within a CMD or DO file. Previously, the CMD file interfered with the input of status responses coming from the ATE client, causing it to act as if no files needed transferring. |
1131.1.3 |
INMEMO.SBR bug fix: The "MEMO LOCK - Hit ESCAPE to abort" message was not being fully cleared once the lock was freed. More importantly, if the job waiting on the lock was using MMO_SIL (silent) mode, it would appear to never come out of the wait if you tried to ESC. |
1131.1.4 |
ATE/VUE bug fix: The keyboard was getting locked at the start of a VUE session, requiring manual release via the Settings menu. (Not sure when this was introduced.) |
1130.1 |
INSTR() bug fix with regular expressions: was returning 0 when the starting pos was more than the length of the pattern string. |
1130.1 |
Compiler fix: SIZEOF(VAR) was not recognizing VAR when it was local or private. |
1130.1 |
ATE server based licensing bug fix: it now allows the server and client to be one day apart (which often occurs when spanning timezones). Previously it would connect but would complain about the date mismatch and would not retrieve the license from the server. |
