Changes in Mar 5th 2014 Version

1. Updated self-installing help file. It shows help topics via online web pages and when those online pages are not available, it uses offline web pages incorporated into the file itself. There are 32MB of compiled HTML in the ProxyHelp.chm file and that has increased size of proxy32.exe executable file.
2. Warn user to "Please, close open dialogs first" when user tries to use hot-key/mouse-kbd-shortcut or open more dialogs.

3. Now AutoHotkey (powerful scripting language to control Windows GUI applications) is installed as part of Proxy32 installation.

   • AutoHotkeyU32.exe script interpreter (together with its help file and AU3_Spy.exe helper) is extracted from internal cab file to . directory (where "." refers to proxy32.exe installation directory) during proxy32 installation.
   • PATH variable in the Proxy32 ENVIRONMENT is modified to contain path to AutoHotkey executable so that script interpreter can be called just by name from any launcher that creates new process.
   • parameter <PROXYHANDLEOFACTIVEWINDOW> is replaced in any launcher by unsigned decimal number that identifies handle of Proxy32 active window
   • parameter <PROXYHANDLEOFACTIVESTICKERWINDOW> is replaced is in any launcher by unsigned decimal number that identifies handle of Proxy32 window that has ""ACTIVE" sticker. Only windows of external processes can have "ACTIVE" sticker. Internal Proxy32 windows (proxy-terminal and proxy-script editor) use red frame instead of "ACTIVE" sticker when they are activated.
   • those two new substitution parameters are introduced to pass window handle to autohotkey scripts via command line parameter.
   • initial Tree.xml (that is loaded if there is no user Tree.xml is found) now contains sample AutoHotkey script to type commands into active window in the Proxy32 Workspace. There is LAUNCH launcher to execute sample ahk script and there is VIEWER launcher to edit sample ahk script.
   • AutoHotkey is well maintained and has open source, so it is a good choice to use for automation of windows of external processes in proxy32 workspace. It can find window by handle even if this window is located inside of (child of) proxy32 workspace window. For comparison, MortScript (another GUI scripting language that is insalled with Proxy32) can only work with top-level windows.