1118.6.1 |
GDI printing fix: The special symbol "%#" (which is supposed to be replaced by the total number of pages in the printout) wasn't working. |
1118.6.2 |
APEX now supports the DELETE switch in SPOOL.SBR, as well as the DELETE command in the printer init files, to delete the file after previewing. |
1118.6.3 |
STATIC & PRIVATE variable initialization bug fix: These variables were getting cleared but not properly re-initialized when re-running a RUN or SBX file from memory (i.e. either due to the automatic cache or the LOAD command.) |
1118.5.1 |
Remove screen warning message "Class Already Exists" when calling the InitCommonControlsEx() function to initialize the Windows Common Dialog Control classes. Apparently the condition occurs in some versions of Windows, but is harmless and not worth bothering the user about. |
1118.4.1 |
AUTLOG.SBR fix: back out change to default buffer size made in 5.1.1117.0 (was causing some kind of interference with the Autolog interface). Note that you can still increase the buffer size (i.e. maximum packet size) by passing the larger packet variable size in the initial AUTLOG call. As a byproduct of the debugging, there are now a number of traces that will appear within AUTLOG.SBR if you set the XDEBUG trace flag. |
1118.3.1 |
APEX / W2K compatibility fix: the buttons on the APEX toolbar to the right of the "Close" button were not appearing at all in W2K. |
1118.2.1 |
Windows printing bug fix: PITCH=AUTO was not adding the LMARGIN value to the line length to compute the required font, thus causing lines to be truncated by the amount of the margin. |
1118.2.2 |
APEX bug fix: A-Shell was hanging in the case where the printfile ended in an unterminated line that contained a FF followed by some other garbage. |
1118.0.1 |
CentOS arithmetic bug fix: Calculations involving B4 variables which had been assigned negative values were not working properly. Although B variables are unsigned, it is legal to assign them negative values, and for the most part, when performing calculations involving other B variables, the results are actually consistent. For example: MAP1 BTOT,B,4 MAP1 BVAL,B,4 BTOT = 100 BVAL = -5 BTOT = BTOT - BVAL
The resulting BTOT should be 105 (100 - -5). But under CentOS, apparently due to a change in the C compiler behavior, BVAL was getting "pinned" to the minimum signed integer of -(2^31), causing BTOT to be set to a very large number. This kind of arithmetic operation is dangerous in the best of cases (any assignment of an intermediate value to an F variable will mess the results up), but we discovered at least one app that was relying on the above kind of calculation working, and which broke when migrating from the -rh8x (Red Hat 8.x) to the -el4 (RHEL 4/5 or CentOS 4/5) version. Note: this fix will also be retrofitted to 5.0.999.8. |
1118.0.2 |
AIX negative/positive crossover fix: Similar to the above issue, there was a problem with calculations involving B or I variables when they crossover over the maximum or minimum value (thereby changing from positive to negative). (This is the same fix as was previously released as 5.0.999.7). |
1118.0.3 |
APEX bug fix: Files with //GDI directives but with no explicit page breaks were causing an infinite loop (creating large output files). (This combination is not recommended, as the preview preprocessor is unable to accurately predict the page break locations that will occur with a particular output device, but it no longer creates havoc.) Also, a minor problem in which a trailing FF in a proper GDI printfile was causing the preview to indicate an extra blank page, even though such trailing FF chars no longer generate a blank page in the real output - see 1117.7 notes below. |
1118.0.4 |
APEX bug fix: The printer init statements LMARGIN and TMARGIN were being ignored. |
