ANNOUNCE: Script Debugger 6.0.5 (6A202)

Script Debugger Beta Testing
#1

Hi Folks,

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

http://www.latenightsw.com/archives/beta_for_script_debugger/ScriptDebugger6.0.5-6A202.dmg

##Changes in build 6A202:

Resolved an expired security certificate issue that prevented clean installations of the 6A200 build.

##Changes in build 6A200:

  • 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 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
#2

Thanks Mark.

It’s working on my macOS 10.12.3 system.

-Chris

#3

I don’t remember the first bug report I sent. It was the day I bought SD, or maybe the day after. And it was related to opening dictionaries. Could you remind me what it was about?

#4