A-Shell Development History

961.3.1   ATE

Fine tuning of type ahead handling.

961.3.2   UNIX

Low level input routine was not handling receipt of 0xFF character properly (generally only a problem in the case of raw data input).

961.3.3   Windows

Switch to latest VS2005 Microsoft development environment. Theoretically, this should not affect executable, but probably there are many subtle effects, hopefully good ones.

961.1.1   XTREE

Enhancement: column sorting now percolates down through all the levels of a multi-level tree. Previously, only the top level items were sorted. Note that in either cases, child rows remain with their parents.

961.1.2   INFLD

Checkboxes: The ||m code (see 958.1 below) now works for fast checkboxes as well as fast combo boxes, causing them to return EXITCODE 13 rather than 0 when they are exited by clicking.

961.0.1   XTREE

Add two switches to cformat:

961.0.2   xcall AUI

Dialogs created with xcall AUI,AUI_CONTROL may now specify a parent ID of -1 to signify that the dialog is a child of the main window. The default (0) makes the new dialog a child of the current dialog, if any.

961.0.3   A-Shell/Windows

Add "Settings" to the text of the File menu options, to reduce user confusion about the meaning of the File options. What previously said "Load," for example, now says "Load Settings."

961.0.4   A-Shell/Windows

A-Shell/Windows command line: the -o <settings file> specification may now contain embedded %env% variables. For example, when sharing a single %MIAME% directory between multiple users that may want to have independent settings without having to change the settings file name, you could use a standard -o parameter of something like:

-o "%USERPROFILE%\Application Data\A-Shell\myapp.ash"

If the specified file is not found, A-Shell will also look for it in the %MIAME% directory, and that isn't found either, it will look for %MIAME%\default.ash. Regardless of which (if any) is found, when the user uses the Settings...Save option to save the settings, they will be written to the location specified by the -o switch. The effect of this is that users may start out sharing their window settings, but as they customize them, they start using their own private settings.

961.0.5   xcall AUI

Dialogs with the MBF_SYSMENU and MBF_MODELESS flags will now also contain a minimize button.

961.0.6   xcall AUI

Dialogs with the MBF_SYSMENU flag now offer additional choices for how it responds to the user clicking on the "X" to close it. By default, that sends an ESC and leaves it to the application to close the dialog (using AUI_CONTROL opcode 3). The new options require setting the MBF_KBD flag, which previously had no effect on dialogs. If you set that flag and put something in the command parameter, then that string will be sent instead of the standard ESC. If you set the MBF_KBD flag but leave the command parameter empty, then dialog will close itself without sending anything to the application. This might actually be very convenient for status/info/debug dialogs that are just outputting auxiliary messages, perhaps via SCRSTS.SBX; in which case further output would just be thrown away.

SCRSTS.SBX 1.0(105) now supports this capability; see the updated TSTSCR sample program (edit 104+) in [907,20] to experiment with it.)

961.0.7   xcall XTREE

Minor timing adjustment in the click-handler to try to eliminate a scenario where a double-click on an XTREE may have a side effect as if a click was issued for a control that is popped or revealed immediately after the exit from XTREE.

Summary Table