939.1.1
(Windows) If -o <ash file> not found, then don't immediately complain but instead look for default.ash in the MIAME directory. If that isn't found, then complain. In edit 939, it complained immediately if the specified ash file wasn't found. Prior to that, it looked for default.ash in the directory specifed by the -o parameter.
The new plan is meant to allow installations to put the default.ash in the standard location, but to allow an alternate ash file and directory to be specified in the command line to accommodate cases where the default ash file is not appropriate. The alternate ash file can be hard coded in the command line for the shortcut, without it mattering if the file exists or not (since it will fall back on the normal default.ash).
939.1.2
Fix a loophole in the hangup (SIGHUP) recovery logic that caused the job to abort when attempting to run a new program. To review, under normal circumstances, if the client workstation is disconnected (e.g. modem or telnet disconnect), the job will become a daemon and continue to run until it stops for keyboard input on its own accord. At that point it will get a Basic error 250, and will be allowed to run until it either shuts itself down or stops for another keyboard input. However, this was only working as long as the job remained in the current program. Now it should be able to continue to chain (or xcall AMOS) new programs while it remains a daemon. (The point of all this fancy business being to allow a critical process, like a posting run, to either complete or shut itself down gracefully in the case of an unexpected disconnect.)
939.0.1
(Windows/ATE) The MBF_ALTPOS scheme for dialog sizing has been revamped, and a new Settings dialog added for adjusting the dialog sizing options. The options are:
| • | Dialog size is based on font size, i.e. MBF_ALTPOS is automatically turned on for all dialogs. |
| • | Dialog size is based on the grid size of the main window, i.e. MBF_ALTPOS is ignored on dialogs. |
| • | Program control, i.e. the MBF_ALTPOS bit continues to work as before with regards to dialogs. (This is the default.) |
As explained before, we believe that the MBF_ALTPOS scheme for dialog sizing (in which the dialog grid size is based on the system font size, and thus is immune to the size of the main window, but adjusts for the resolution and font size of the Windows desktop) is superior to the old scheme (based on the grid of the main window). But, it seemed that no one agreed with us, mainly because when they switched to the new scheme, existing dialogs "looked funny". After some study, we have determined that we can correct for this by allowing you to adjust the horizontal and vertical scale factors to match the implicit aspect ratio of your assumed working environment.
Originally, we had hard-coded those scale factors as 120% of the combobox height and 120% of the average character width. The new defaults are 100% of the combobox height and 160% of the average character width. But if you find that this results in dialogs that are too short and wide, or too tall and narrow, then you can adjust accordingly.
The other difference noticed when switching to the MBF_ALTPOS scheme was that there was approximately one additional row of space at the bottom of the dialog. We've removed the extra row, so that in most cases, the amount of extra space at the bottom of a new-style dialog is pretty close to what it was before. (Only now it is more consistent, regardless of the dialog size or resolution, whereas before it was affected by both, such that a dialog of 400x600 may have had just the right amount of bottom margin, whereas if you displayed the same dialog at 1024x768, it would have had too little or too much.
Warning: This means that if you were using MBF_ALTPOS to size your dialogs, you now need to add 1 to the ending row coordinate! (We normally try to avoid these kinds of changes, but it appears that virtually no one was using MBF_ALTPOS in this way and thus the effect change would not harm anyone.)
With the new ability to experiment with the settings without touching the program source code, it is hoped that developers will give this issue another round of consideration and ultimately arrive at the same conclusion that we did, that sizing the dialogs based on the system font size rather than on the grid size of the main window makes much more sense and will result in dialogs that "work" in a much wider range of display environments.
939.0.2
ATE now shows kbd locked status properly on the Settings menu even when locked internally during an ATE command. (Previously it didn't, and if such a command aborted, it would leave the kbd locked but confuse the operator by not showing it locked.)
Also, fix a problem in which hitting a "D" as the first character after connecting to certain systems could cause it to disconnect. (This was related to the fact that the kbd sequence "|D" will normally disconnect.)
939.0.3
(Windows/ATE) EPRINT controls are no longer protected from erase by TAB(-1,9) and TAB(-1,10).
939.0.4
(Windows/ATE) INFLD combo box now reduces the height of the dropdown list when font scaling is used, in order to avoid overlapping the dropdown button. (Otherwise the default is to show 30 items.)
