LNS Home
Script Debugger
Download & Buy
x Explore
x Edit
x Run & Debug
x Deploy
What's New In 4.5
bullet Documentation
bullet Blog Posts
My SD Story
Software Updates
4.0.9 Update
3.0.9 Update
bullet 2.0.5 Update
x Free Downloads
XML Tools
XSLT Tools
x Property List Tools
x List & Record Tools
Register Your Copy of Script Debugger
Join the Script Debugger Mailing List
x AppleScript/ Scripting Links
x Script Debugger 4.5
Site Contents
bullet Mark’s Blog
Product Registration
Bug Reporting
x Freeware
Contacting Us

SD4 Headling




Most scripts, when run, will implicitly or explicitly generate a result. This result is entered into the script window’s result drawer, in the top pane (the result pane) of the drawer.


A Debugger preference lets you set what happens when a script completes running (“Show result when scripts pause or end”):

  • No. If the drawer is not open, it does not open automatically. To summon the drawer manually if it isn’t open, choose Script > Show Result (or click the Show Result button in the toolbar).

  • Show Result Drawer. The drawer opens, if necessary, revealing the result. This is the factory default setting, and will probably best suit most people’s way of working. Seeing the result drawer has certain advantages. Not only do you see the result, but you also view persistent variables and execution times.

  • Show Result Viewer window. The result is displayed in a separate viewer window — in fact, it is the very same viewer window you can summon manually by choosing Script > Show Result in Viewer.

An Editor preference lets you set whether the open or closed state of the result drawer should be remembered when a script is saved and restored when it is next opened.

The open or closed state of the result drawer is one of the window features that you can configure by setting the default state for all new script windows.

The result pane is a viewer, with many capabilities and view options. In particular, when the result is an object reference, the result pane in Best view is an explorer view. Script Debugger probes this object reference to obtain its elements and properties and their values when the result is generated. This feature is very informative and can reduce your script development time. So, for example, consider this script:

tell application "Finder"
    get desktop
end tell

The result is the reference desktop of application "Finder", but in Best view the result pane shows you more than this — it shows you all about the desktop at this moment:


Moreover, since this is an explorer, you can do all the things in the result pane that you can do in any explorer. Not only can you separate off the result pane itself as an individual viewer window (by choosing Script > Show Result in Viewer); you can separate off any entry within the result as an individual viewer window. You can drill down the hierarchy within the explorer, you can transfer references and values from the explorer to your script, you can ask for a dictionary definition, and you can even alter values in real time, thus affecting the running target application.

Further Details:

Explore | Edit | Run & Debug | Deploy | What's New In 4.5 | My SD Story

Copyright © 1998-2009 Late Night Software Ltd. - All Rights Reserved.