Probably the biggest change in Macro Scheduler 11, though not visual, was Unicode support. For Macro Scheduler to support Unicode in scripts it has to save the script files with Unicode encoding rather than ANSI encoding. And if you open a Unicode file up in an ANSI editor it’s going to look garbled. Since older versions of Macro Scheduler were ANSI only and didn’t know anything about Unicode, if you open a v11 script up in v10 (or earlier) that script is going to look wrong.
The v11 release notes have a big warning about this. Nothing is damaged permanently and it doesn’t have any effect on upgrading. It’s only an issue if you edit or create a script in v11 and then, for whatever reason, try to open it in an earlier version. So if, for example, you’re running v11 and you have another PC running v10 and you create a script on your PC and wish to open it on the PC running v10 it’s going to look messed up.
One solution of course is to upgrade that copy of v10 to v11. But there is another solution. You can tell v11 to save the script with ANSI encoding. From the editor use File/Save As and then in the file type box select “ANSI Script Files”. Alternatively just open the script file up in Notepad and save it again, selecting ANSI in the Encoding box. This of course assumes that you don’t actually NEED Unicode. If you have Unicode characters in your script which you need to use, then clearly saving as ANSI will destroy them. In which case you do need to upgrade that v10 installation to v11.
