You can debug most AppleScripts this way just fine. Normally, to use Script Debugger, you select or double-click an AppleScript file and it opens up, ready to go to work.
AppleScript Code (handler being debugged).Produce code that can handle both versions of Excel.Separate code for two different versions of Excel.
I can watch what happens one step at a time and can make quick fixes and then re-run. When it failed, I could identify the problem with little guesswork. At last I was able to see what was going on as the script progressed. When I met Script Debugger, I gave a huge sigh of relief. I’ve used lots of interactive symbolic debuggers in my time and Script Debugger replicates the best features of most of them, particularly single-stepping and variable examination and editing. Anoher alternative is Display Dialog, which is widely discouraged for debugging.Įnter the Script Debugger. Debugging scripts in Script Editor forces the developer to use lots of log messages which can only be comfortably reviewed after the script is complete. Apple’s Script Editor, however, leaves something to be desired. While it’s been billed as closer to “natural language,” I find it a bit quirky, but I’m slowly getting used to it. Debugging an AppleScript Handler in VBA Script Debugger vs Apple’s Script EditorĪppleScript is designed to help automate simple tasks that you need to do often, without the need for learning a high level language like Objective C.