Script Debugger 2.0.2/2.0.3 Release Notes

Script Debugger 2.0.3 is a maintenance release that introduces a number of new features and addresses a series of issues that came to light following the release of Script Debugger 2.0.

New Features | Bug Fixes | 2.0.1 Release Notes

Release Notes

In addition to the the changes made for Script Debugger 2.0.1, Script Debugger 2.0.3 introduces the following new features and bug fixes.

New Features

The following new or altered features appear in Script Debugger 2.0.2/2.0.3:

• Palette windows now carry a title showing the name of the active palette.
• You can now set the default size of new script windows using the new Set Default Window Size command in the Edit menu.
• The behavior of the "Send Unhandled Events To Document" preferences setting has been changed. In past versions of Script Debugger, this setting controlled the handling of events directed at the Script Debugger application and events directed to specific script documents. In version 2.0.2, the preferences setting only affects events directed at the Script Debugger application. Unhandled events targeted at a specific document are always processed by the script. This makes invoking AE handlers in scripts much simpler and more reliable.
• Script Debugger's Applet Shell Plug-In facility has been upgraded to version 1.1, allowing Applet Shell plug-ins to write to the data fork when building an applet or droplet. Script Debugger 2's Applet Shell Plug-in facility is described on our web site at http://www.latenightsw.com/sd2.0/developer.html.
• Script Debugger's Table Of Contents menu and the Go To Next/Prev Handler commands now support JavaScript scripts. Late Night Software offers an OSA (Open Scripting Architecture) version of JavaScript for those who prefer JavaScript over AppleScript. Details are available on our web site at http://www.latenightsw.com/freeware/JavaScriptOSA/.

Bug Fixes

Script Debugger 2.0.3 addresses the following:

• A cosmetic problem involving selection highlighting that occurred when activating Script Debugger windows with multiple split-panes has been resolved.

Script Debugger 2.0.2 addresses the following:

• A bug in the Remove Comments script that caused the script to incorrectly remove -- style comments has been resolved.
• The Table Of Contents menu now correctly handles the case where a "pipe" style identifier appears in a (* *) style comment block. In previous released, this kind of comment could prevent handlers declared following the comment from appearing in the Table Of Contents menu.
• The Apple Event Log window no longer stops logging information when the log grows too large. Also, Apple Event logging has been improved to allow the Script Debugger User Interface to remain responsive even when a lot of logging activity is taking place.
• Script Debugger now fully conforms to the Macintosh User Interface guidelines regarding the handling of mouse clicking and dragging of icons in window titles.
• It is now possible to write attachment handlers for the Quit AppleEvent.
• It is now possible to access text, word, line and character objects from window objects in Script Debugger's AppleEvent interface. For instance, get length of text of window "Apple Event Log" now works.
• A problem in Script Debugger's AppleScript Debugger that caused coercion errors to occur when object specifiers were passed as parameters to handlers has been resolved.
• A crashing bug that occurred when an if expression then return statement appeared outside a handler declaration (i.e. in a script's implicit Run handler) has been resolved.
• Script Debugger no longer creates damaged applets when a save AppleEvent containing an as script application parameter is applied to a text or compiled script document.
• A cosmetic problem that occurred when resizing windows to a smaller size with line wrapping enabled has been addressed.
• The Dictionary Explorer is now more compatible with AppleWorks 6. The Explorer can now show the elements of the drawing area document property.
• Variable viewer windows are no longer automatically closed when the variable's value becomes undefined.

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