Download

Release Notes

This maintenance release attempts to resolve the stability problems that some Script Debugger users have experienced on Snow Leopard. While I have made progress improving stability, there is still more to be done. This maintenance release addresses a number of other important issues so I decided to make these fixes available now rather than hold the release back while I continue resolving the stability problems.

A big thank you to all the folks who downloaded the various Script Debugger 4.5.5 Beta builds. I really appreciate all the great feedback and bug reports I received.

UPDATE: I have released Script Debugger 4.5.6 which resolves a license limit exceeded error that effected some users. In all other ways, 4.5.6 is identical to 4.5.5.

XML Tools 2.9.4

Property List Tools 1.0.7

List & Record Tools 1.0.6

I am preparing another Script Debugger 4.5 maintenance release.

I have been struggling to resolve some stability problems ever since the release of Script Debugger 4.5. Resolving these issues has been very difficult as I’ve not been able to reproduce several of the crashes on my own systems. The Script Debugger 4.5.5b3, b4 and b5 releases have resolved several crashes, but some problems remain. The Script Debugger 4.5.5b6 build addresses some additional problems that I hope will further improve stability.

To help me determine if I’ve resolved the stability issues (or at least improved things), please allow Script Debugger to submit ALL crash reports. I know that this may slow you down a little, but it will help me as I work to finally resolve the stability problems.

Requirements

• A Script Debugger 4.5 registration number
• Intel or PowerPC Macintosh
• Mac OS X 10.6, 10.5, 10.4

Download

Script Debugger 4.5.5b6 (11.4MB)

Installation

• Quit Script Debugger if it is running
• Mount the SD4.5.5 disk image
• Copy the Script Debugger 4.5 application from the disk image to your Applications folder (or any other place on your disk)
• Restart your Macintosh to ensure all caches are flushed

I recommend keeping your copy of Script Debugger 4.5.4 around in case you need to revert to that build. Note also that this BETA build expires on September 1, 2010.

Script Debugger 4.5.5b6 Changes

• 14907 [Crash] Improved the Explorer to protect against some more instances where the UI thread may be accessing data while background threads are altering the data.
• 14927 The Script Debugger 4.0 OSA component is removed if it is still present to avoid the possibility of memory corruptions that might destabilize Script Debugger 4.5.
• 14928 Script Debugger auto-saves documents each time they are compiled. This may slow things down slightly, but it will improve Script Debugger’s ability to recover the contents of open documents in the event of a crash. Previously, Script Debugger auto-saved only before a document was executed.
• 14926 When exporting a Run-Only script over an existing file, Script Debugger ensures that pre-eisting recovery and QuickLook preview data is removed.
• 14925 This change addresses a regression in bug 14881. Script Debugger no longer reports 32-bit scripting addition warnings for StandardAdditions.osax when saving on 32-bit machines as StandardAdditions.osax will always be fully compatible with the host hardware. Script Debugger now only does 32-bit scripting addition checking when running on Mac OS X 10.6 or later.
• 14885 FontSyncScripting.app is no longer mistaken as a Scripting Addition.

Script Debugger 4.5.5b5 Changes

I am preparing another Script Debugger 4.5 maintenance release.

I have been struggling to resolve some stability problems ever since the release of Script Debugger 4.5. Resolving these issues has been very difficult as I’ve not been able to reproduce several of the crashes on my own systems so I’m debugging in the blind. The Script Debugger 4.5.5b3 and b4 releases have resolved several crashes, but some problems remain. The Script Debugger 4.5.5b5 build addresses two additional crashes.

To help me determine if I’ve resolved the stability issues (or at least improved things), please allow Script Debugger to submit ALL crash reports. I know that this may slow you down a little, but it will help me as I work to finally resolve the stability problems.

Requirements

• A Script Debugger 4.5 registration number
• Intel or PowerPC Macintosh
• Mac OS X 10.6, 10.5, 10.4

Download

Script Debugger 4.5.5b5 (11.4MB)

Installation

• Quit Script Debugger if it is running
• IMPORTANT Delete all copies of Script Debugger.component and Script Debugger 4.5.component from your ~/Library/Components folder
• Mount the SD4.5.5 disk image
• Copy the Script Debugger 4.5 application from the disk image to your Applications folder (or any other place on your disk)
• Restart your Macintosh to ensure all caches are flushed

I recommend keeping your copy of Script Debugger 4.5.4 around in case you need to revert to that build. Note also that this BETA build expires on September 1, 2010.

Script Debugger 4.5.5b5 Changes

• 14907 [Crash] Improved the Explorer to protect against some more instances where the UI thread may be accessing data while background threads are altering the data.
• 14899 [Crash] Resolved a bug that caused Script Debugger to crash when AppleScript reports error text ranges that lie beyond the end of the script. This happens most commonly when you have an unclosed quoted string within a block comment.

Script Debugger 4.5.5b4 Changes

I am preparing another Script Debugger 4.5 maintenance release.

I have been struggling to resolve some stability problems ever since the release of Script Debugger 4.5. The rate of crash reports has diminished significantly with the Script Debugger 4.5.5b3 beta build, but I’m still getting a few crashes. This new beta build contains fixes for a few more instances where AppleScript may be causing crashes.

To help me determine if I’ve actually solved the stability issues (or at least improved things), please allow Script Debugger to submit all crash reports. I know that this may slow you down a little, but it will help us all as I work to finally resolve the stability problems.

Requirements

• A Script Debugger 4.5 registration number
• Intel or PowerPC Macintosh
• Mac OS X 10.6, 10.5, 10.4

Download

Script Debugger 4.5.5b4 (11.4MB)

Installation

• Quit Script Debugger if it is running
• IMPORTANT Delete all copies of Script Debugger.component and Script Debugger 4.5.component from your ~/Library/Components folder
• Mount the SD4.5.5 disk image
• Copy the Script Debugger 4.5 application from the disk image to your Applications folder (or any other place on your disk)

I recommend keeping your copy of Script Debugger 4.5.4 around in case you need to revert to that build. Note also that this BETA build expires on September 1, 2010.

Script Debugger 4.5.5b4 Changes

• 14898 More changes that attempt to resolve Script Debugger’s stability issues (Please ensure you have deleted all old copies of Script Debugger.component and Script Debugger 4.5.component from your ~/Library/Components folder).

Script Debugger 4.5.5b3 Changes

After several attempts to make Affrus 1.0 work on later Snow Leopard, I gave up. Affrus 1 was built using CodeWarrior and Carbon and the transition to Xcode and modern versions of Carbon proved too difficult. However, I can report that over the last few months, work has resumed on Affrus 2.0 which is a re-implementation of Affrus using Xcode and Cocoa.

Here’s a screenshot of the work to date running on Snow Leopard:

I am being deliberately circumspect about describing the product’s features and system requirements to avoid breaking any promises when the product is finally released.

I am not yet at a point where I feel comfortable inviting Beta testers to use the product, but it won’t been too much longer.

I am preparing another Script Debugger 4.5 maintenance release.

I have been struggling to resolve some stability problems ever since the release of Script Debugger 4.5. I thought I had these problems resolved a couple of times, but they persist. With the release of Mac OS X 10.6 they seem to have gotten worse.

For the Script Debugger 4.5.5 maintenance release I want to try and resolve these stability issues once and for all. The difficulty is that I cannot reproduce any of these crashes here on my systems, and the crash reports that I receive don’t point to any obvious causes.

I had a bit of luck and was able to find and resolve some memory management errors in Script Debugger which may have contributed to the problem. I’ve also identified a problem in AppleScript that may also be contributing to the stability issues.

To help me determine if I’ve actually solved the stability issues (or at least improved things), please allow Script Debugger to submit all crash reports. I know that this may slow you down a little, but it will help us all as I work to finally resolve the stability problems.

Requirements

• A Script Debugger 4.5 registration number
• Intel or PowerPC Macintosh
• Mac OS X 10.6, 10.5, 10.4

Download

Script Debugger 4.5.5b3 (11.4MB)

Installation

• Quit Script Debugger if it is running
• IMPORTANT Delete all copies of Script Debugger.component and Script Debugger 4.5.component from your ~/Library/Components folder
• Mount the SD4.5.5 disk image
• Copy the Script Debugger 4.5 application from the disk image to your Applications folder (or any other place on your disk)

I recommend keeping your copy of Script Debugger 4.5.4 around in case you need to revert to that build. Note also that this BETA build expires on September 1, 2010.

Script Debugger 4.5.5b3 Changes

• 14898 Several changes that attempt to resolve Script Debugger’s stability issues and reduce memory leakage when closing documents (Please ensure you have deleted all old copies of Script Debugger.component and Script Debugger 4.5.component from your ~/Library/Components folder).
• 14886, 14151 Corrected a series of issues that prevented the Manifest command from properly detecting AppleEvents sent to applications. Note that these fixes also restore Script Debugger’s ability to detect which applications will be launched when opening scripts.
• 14885 FontSyncScripting.app is no longer mistaken as a Scripting Addition.
• 14884 Script Debugger’s logic for opening scripts with incorrect filename extensions has been improved. For instance, compiled scripts carrying a ‘.applescript’ extension will open correctly (.applescript normally indicates a plain text file).
• 14881 A new 32-Bit Only option has been added to the Save As panel allowing you to create 32-Bit applets directly from Script Debugger (this avoids having to visit the Finder’s Get Info window to select the 32-Bit Only execution option).
• 14853 Script Debugger can now open the iCal dictionary and any other application dictionaries which make use of xinclude directives.
• 14883 Script Debugger now reports error information in the AppleEvent Log window.

Download

Release Notes

The remaining Scripting Addition, XSLT Tools, has proved to be a difficult problem to solve. XSLT Tools makes heavy use of Carbon APIs that are not available to 64-bit builds on Snow Leopard. However, even the existing 32-bit version crashes on Snow Leopard systems.

Here is a new 32-bit Snow Leopard/Intel only build of XSLT Tools that no longer crashes:

XSLT Tools 2.1.3b1

In order to use this version of XSLT Tools, you need to run the AppleScript Script Editor, applets and droplets in 32-bit mode. This is done by modifying these files using the Finder’s Get Info panel and then checking the 32-bit mode checkbox.

UPDATE: Script Debugger 4.5.4 has been released.

Requirements

• A Script Debugger 4.5 registration number
• PowerPC or Intel Macintosh
• Mac OS X 10.4, 10.5, 10.6

Download

Script Debugger 4.5.4b4 (11.4MB)

Installation

• Expand the SD4.5.4 archive
• Quit Script Debugger if it is running
• Move the Script Debugger 4.5 application to your Applications folder (or any other place on your disk)

I recommend keeping your copy of Script Debugger 4.5.3 around in case you need to revert to that build. Note also that this BETA build expires on February 1, 2010.

Script Debugger 4.5.4b4 Changes

• 14870 Corrected a problem that caused the insertion point to be in wrong place when dragging items to the last line of a script.
• 14869 Corrected a series of parsing bugs that sometimes caused parts of scripts to be omitted from the Table Of Contents menu.

Script Debugger 4.5.4b3 Changes