#Script debugger mac set file properties code#

#Script debugger mac set file properties code#

When this is executed, the mainline code runs and calls the handler, just like other languages call subroutines. Set AppleScript's text item delimiters to oldDelimiters - restore the original settingĪ handler is not run unless invoked by mainline. Set theArray to every text item of theString - create the array Set AppleScript's text item delimiters to theDelimiter - set delimiters to delimiter to be used Set oldDelimiters to AppleScript's text item delimiters - save delimiters to restore on completion Local oldDelimiters, theArray – allows local variables to be seen by the debugger Set SplitArray to split('String 1|String 2|String 3', '|') Here’s an example of a handler that splits a string based on a delimiter. Easy as pie.ĭebugging a handler (Apple’s term for what the rest of us might call a subroutine) is comfortably handled by Script Debugger. That’s when we need what I term Indirect debugging.īoth are described in detail in the following sections.įor most scripts, all you have to do is turn on the debugger and single-step through, or set breakpoint(s) and run till they pause the execution. Sometimes invoking a script, already debugged using the direct method, from another application like VBA, can cause unexpected problems. 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.Pass parameters from VBA to AppleScript handlers.Debug your AppleScript scripts when called from Microsoft Excel VBA (Visual Basic for Applications).So this is a longer, but more complete coverage of the concept. It turned out to be more complicated than I thought, due to differences in calling sequences between Excel versions. I initially started to write a simple how-to for debugging a VBA-to-Applescript connection. 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.