Macro Scheduler 9.0 Beta has just been made available for testing to registered users. For details on how to download and for a list of new features check out the beta forum.

As you can see, Macro Scheduler now has a new icon. Yes, in a way, this is a sad day. The grey, trusty old cog wheel that has been with us for almost ten years has now made way for a new, bright young thing. Staying with the mechanised theme, Macro Scheduler now has a bright, vibrant sprocket with a higher colour depth and resolution for modern operating systems like Vista. So let us bid farewell to old cog and welcome in the new icon.

You’ll find a full list of what’s new in the forum, but the emphasis with this new version is on making the software easier to use and streamline the creation of scripts. We’ve updated and overhauled the macro builder on the Macro Properties dialog as well as the Script Editor to make script writing easier for novices as well as experts. A new Command Locator and Code Builder makes it easy to find the function you want and insert the code without having to remember the syntax or look it up in the help file. The Code Builder prompts you for the parameters and options that are needed. Syntax QuickHelp shows you the syntax as you edit, and the Inline Function Selector gives you a choice of functions/commands as you type. Code Snippets in the editor allows you to store often used pieces of code for quick insertion later.

In terms of the Scripting Engine we’ve added new commands, such as the Telnet scripting commands and improved the FTP commands to support multiple files. And expert coders will appreciate the IGNORESPACES directive. But my favourite improvement is the introduction of the Image Recognition functions, taken from the Image Recognition Library and now native to MacroScript and therefore easier to use. I don’t think I anticipated how useful the Image Recognition Library would be when it was released. For many people it has transformed the way they write automation scripts. Image Recognition allows the macro to “see” the screen and locate objects visibly – just like how a human uses the computer. This means any application can be automated, regardless of its underlying technology/interface. You can even automate remote applications running on non-Windows operating systems. So I think merging the Image Recognition Library into the language is an important step. And soon, hopefully, I might have some more news to share in regards to Image Recognition and automation script development …