ANNOUNCE: Script Debugger 6.0.5 (6A200)

Update: It looks like there’s a problem with this build. A new one will be forthcoming…

Hi Folks,

Here’s a new Script Debugger 6.0.5 build. You can download the new build here:

##Changes in build 6A200:

  • 763: 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 document property of the script window object.

  • 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.

1 Like

Hey Mark,

When I install and launch this latest build macOS 10.12.3 reports it is damaged.


Same here in 10.12.4. Following Apple’s instructions to bypass security step by step gives the same result.

Yes, it looks like there’s a code-signing issue with this build.

No problem here

–>Script Debugger 6.0.5 (6A200) on Mac OS 10.11.6 (15G1421)

I got this message. I’m a Myriad Tables addict, if I can’t use it here, I’ll revert to the previous version!

Myriad Tables Lib is not compatible with this version of Script Debugger. You can cancel, or you can enter row numbers, separated by commas, to simulate showing the dialog and selecting those columns.

When I clicked “Simulate” it seemed to display the table, but then when I continued I got this:

“The operation couldn’t be completed. dyld: warning, LC_RPATH @executable_path/…/Frameworks in /Users/stocklys/Library/Script Libraries/Myriad Tables Lib.scptd/Contents/Frameworks/SMSTableDialogBuilder.framework/SMSTableDialogBuilder being ignored in restricted program because of @executable_path
/Users/stocklys/Library/Application Support/Script Debugger 6/Scripts/008)Open a FolderFrom Favoites.scpt: execution error: User canceled. (-128)”

This was from an MT script called from SD’s Scripts menu.

Yes, I think there might be changed requirements in 10.12.

There will be a new version of MT shortly. The test for Script Debugger’s capabilities makes an assumption that falls foul of the new way of running scripts in the Scripts menu.

Mark, just so you know, when you update a post, the Discourse forum SW does not sent out email notifiers.

Thanks for responding so quickly.