We are pleased to announce the release of Script Debugger 6.0.5. Script Debugger 6.0.5 is a free maintenance release addressing a series of issues that came to light following the release of Script Debugger 6.0. This maintenance improves Script Debugger compatibility with macOS Sierra (Mac OS X 10.12) and addresses a number of stability and performance issues.
You can download Script Debugger 6.0.5 from within Script Debugger using the Check For Updates menu command within the Script Debugger menu or you can download it directly from our Free Trial page.
Changes in the 6.0.5 release:
771: Applets in the Scripts menu are now launched rather than run by the system script runner.
773: Fixed a crash that could occur when closing documents on Macs with Touch Bars.
769: User canceled errors in scripts run from the Scripts menu will no longer result in error dialogs.
764: Fixed regression in display of linebreaks and tabs in results explorers.
770: Corrected regression where opening a script library via the Open Viewer command when the Open In Tabs preference setting is enabled results in a new window being created.
765: Text selection range is restored when opening a script in a new tab.
768: It is now possible to change the current tab via scripting by setting the
current documentproperty of the
757: Addressed a crashing bug that occurs when AppleScript begins returning the errOSAInternalTableOverflow error.
753: Several changes have been made to the way script documents are opened, particularly when opened via a script.
When opening a document via script, the command will return as soon as the document is open, and not after a 5 second delay.
The open command will return references to any script documents opened, and if the command specifies script dictionaries, reference to the dictionary windows.
If you open several scripts’ dictionaries at once via scripting, the first will open in any existing dictionary window or a new window, and the rest will open in separate dictionary windows.
When you try to open a document via a script and there is an error — for example, if the script was saved run-only — the error will no longer cause a modal dialog to appear in Script Debugger, but will instead be returned just as a scripting error. This means you can now wrap opening documents in a try block.
If a script document has a scripting definition file, you can now have both the script and the dictionary open at the same time.
Scripts in Script Debugger’s Scripts menu will now be run in a process separate from Script Debugger. This has several consequences:
Scripts targeting Script Debugger will require explicit tell blocks.
When scripts are running, you will see the small spinning gear in the menu bar that you see when running scripts from Apple’s Scripts menu. Any use of Apple’s progress properties will display in the same area.
Script that try to use AppleScriptObjC to modify the host’s behavior will have no effect on Script Debugger.
Scripts with crashing errors, especially AppleScriptObjC errors, will no longer crash Script Debugger.
Running scripts that open documents in Script Debugger will no longer generate spurious timeout errors.