********* WinBatch, WinBatch+Compiler and WeBatch 2015B Released *********

Started by td, July 29, 2015, 11:44:12 AM

Previous topic - Next topic


We have just released WinBatch, WebBatch and WinBatch+Compiler 2015B.

Customers on an active maintenance plan may download the latest version of the software from the download page.


If you do not have a current maintenance plan and are interested in getting updated, please visit our software maintenance renewal page. You can easily order online.


DLL 6.15bob First showing up in WB 2015B

    Modified COM exception error reporting to display a system error number in the 'More Error
    Info' dialog when text based exception information is not provided by the COM server
    reporting the exception.

    Modified setup.exe to allow the installation of WinBatch or WebBatch on install target hard
    drives or shared folders with more than two terabytes of free space.

    Added new optional parameter to the SendKey, SendKeyTo, and SendKeyChild functions.  Use
    the new parameter to indicate the number of seconds to delay between keystrokes sent to the
    currently active or targeted window. Use a floating point number for the paramter's value
    to indicate partial second values.  When the parameter is used in a call to one of these
    functions, the value overrides any keystroke timing value set using IntControl 35 for the
    duration of the function call.  If the char-string paramter of these functions contains
    only one key value, the delay will occure after the keystroke is sent to the keyboard
    driver but before the function returns.
    Added Windows 10 OS support to the manifests of all distributed executables.

    Modified the 'Two Explorers, side by side' menu item for both PopMenu and FileMenu so that
    the menu item functions properly on Windows 10.

    Added support for the LPVOID, LPCSTR, and LPCWSTR data type names in structure descriptor
    strings passed to the DllStructAlloc function. Also added support for structure members
    declared as pointer using a supported type name followed by an asterisk (*) character.
    Note that the DllStructPeek and DllStructPoke functions do not perform any interpretation
    of the contents of the memory location contained in a member with an asterisk modified data
    type or the LPVOID data type.
    Structure members declared as LPVOID or with an asterisk modifier will usually either
    contain or should be set to a valid memory address or 0 depending on the requirements of
    the DLL function using the structure.  See IntControl 32, IntControl 42, and IntControl 98
    documentation for more information about using raw memory addresses in WIL scripts.

    Modifed the the WIL COM subsystem to workardound a defect on some versions of Windows in
    the WMI service COM Automation exception reporting.
    New Function:                                             
           The function returns a @TRUE(1) when a window is associated with a Windows Runtime
           App (Window Store App.) For most non Runtime windows, it returns @FALSE(0).  Windows
           associated with system processes, like the Windows shell's 'File Explorer' , do
           cause the function to return @True even though the processes are not Windows Runtime
           Apps. The function always returns @FALSE on Windows 7/2008 R2 and older versions of
           "partial-winname" - A window name that can be either an initial portion of, or an
                               entire window name.
           The function only works with top-level (parent) application windows.

        WinMacro, the WinBatch macro recorder, returns as a menu option in PopMenu's main menu
        on Windows Vista/2008 and newer versions of the Windows operating system. WinMacro
        required extensive internal modifications to make it possible to record and playback
        macros on newer versions of Windows. These changes impact both the behavior of
        WinMacro's user interface and the user input events WinMacro can record and playback.
        The user interface behavior changed in the following ways:
            When the "Edit Script" toolbar button or "Edit" menu item is selected WinMacro now
            automatically creates a script file version of the selected macro.
            Once a script file for a macro has been created, WinMacro will always load and
            execute the script version of the selected macro when the "Play" toolbar button or
            menu item is selected.  This means that any modifications made to the script are
            always reflected during macro play back unless the "Save Macro as WinBatch Script"
            options is unchecked in the "Save WinMacro Macro" dialog. When the option is
            unchecked, WinMacro will play back the original macro as recorded.   
            It is no longer possible to change the playback speed after a macro is recorded.
            The playback speed must be set before recording a new macro.
            If WinMacro cannot find the script file version of macro previously converted to a
            script, the macro cannot be played unless the "Save Macro as WinBatch Script"
            options is unchecked in the "Save WinMacro Macro" dialog.
        WinMacro now performs all macro playback using the WIL interpreter.  This means that
        only mouse movements, mouse button clicks, and key strokes are recorded. Mouse button
        support is confined to the left and right mouse buttons. Other mouse buttons including
        scroll wheel rotation or clicking are not subject to recording. The Window key is
        supported but holding down the Windows key while repeatedly pressing another key is
        interpreted as individual combined key events. This means that pressing and holding the
        Windows key while repeatedly pressing and releasing the tab key cannot be recorded and
        then used to cycle through currently running application windows on playback.  Non
        standard keyboard keys like the 'Fn' key found on many notebook computers are not

        The format of the macro archive file (.waf) has changed.  This change means that macros
        recorded using the old WinMacro application can still be played on an Windows XP/2003
        system using the new WinMacro but new macros cannot be added to old style archives
        using the new WinMacro. In order to record new macros on Windows XP/2003 a new archive
        must first be created.

        The new WinMacro requires Windows XP or newer and cannot be used on Windows 2000 or
        older versions of the Windows operating system.

"No one who sees a peregrine falcon fly can ever forget the beauty and thrill of that flight."
  - Dr. Tom Cade