Tuesday, May 4, 2021

Script Debugger 8

Late Night Software (full release notes, press release):

Script Debugger’s appearance has been updated to fit nicely into macOS Big Sur. Script Debugger 8 runs natively on Apple’s new M1 Macs, and generates universal Intel/ARM applications when running under macOS Big Sur, regardless of platform.


To go along with Dark Mode support, Script Debugger 8 provides user configurable and switchable themes.


Viewing script library documentation has been made much easier with the introduction of a Libraries section within Script Debugger’s dictionary window.


Script Debugger 8 offers vastly expanded options for generating standalone applications, along with the ability to code-sign and notarize applications.


Security changes introduced in macOS Mojave and later rendered Script Debugger’s external debugging feature inoperable. For Script Debugger 8 we’ve removed external debugging[…]

There’s something weird going on with AppleScript on Apple Silicon Macs. I and others have encountered problems where AppleScript commands time out and fail when either the sending or receiving app is running in Rosetta. So it’s great news that my preferred AppleScript editor now runs natively.

It’s $100 or $50 to upgrade, with many of the features working in the free lite mode.


4 Comments RSS · Twitter

Beatrix Willius

The problem are the affected apps in Rosetta and not the app that is executing the script. So a universal Script Debugger doesn't make a tiny bit of difference.

However, the fruit company told me that the AppleScript bug in Rosetta should be fixed in 10.4.

not directly related, but maybe some kind soul will take pity on me.

many years ago, i wrote an applescript that saved its own window position, and restored it the next time it was run. no doubt i used an applescript property variable to save the location between runs. but i cannot for the life of me remember how i did it, and i cannot find an example. every search i try for "applescript window position" or similar gets me a script that is manipulating the window position of some other app, rather than the applescript itself.

seems like something i should just be able to puzzle out, but applescript syntax is so unbelievably undiscoverable that such a tactic never works for me.

@Beatrix I initially thought that the problem was confined to when the receiving app was in Rosetta, but then I ran into it the other way, too. And the second two cases that I linked to are with the sending app running in Rosetta.

Glad to hear that the bug will be fixed. When I reported it to Apple they said they hadn’t seen it before and couldn’t reproduce it even with the test app that I wrote.

@Allen The script itself is just a document. You would need to get the bounds of the window in the app that has opened the document.

@Allen: Late Night Software has a great forum where you can get help on questions such as yours, if you need more help.


Leave a Comment