We are pleased to announce the release of Script Debugger 8.0.9. Script Debugger 8.0.9 is a free maintenance release addressing a series of issues that came to light following the release of Script Debugger 8.0.

This update can be applied using Script Debugger’s Check For Updates command (in the Script Debugger menu). Alternatively, you can download the latest version of Script Debugger.

• Resolved an issue where code folded block comments (* ... *) cannot be unfolded.
• Resolved a crashing bug that happens when compiling a using terms from application or tell application block where the application name is an empty string while debugging is enabled.
• Corrected a problem where clearing a menu item key bindings does not actually clear the key binding the next time Script Debugger is launched.
• Resolved a problem where key shortcuts assigned to menu items within the Export Run-Only menu are not properly retained.
• Resolved an error in the handling of # end-of-line comments embedded within a (* ... *) block style comment. See this forum posst for more details.
• Resolved a problem where Script Debugger may crash when launching on Sequoia systems.
• There is a new expert preference PrefShowLSHandlerRankDialog. When this preference is set to YES, when a script contains an open handler and it’s Bundle Settings lists one or more UTIs to be accepted, a new dialog will appear when exporting a run-only applet (Apple or Enhanced) via the File -> Export Run-Only menu command.
  
  The dialog will let you choose whether to give the UTIs an LSHandlerRank value of None or Default. Script Debugger normally uses None, which is the safest option for scripts. Choosing Default may result in your script launching when a document is double-clicked, with unintended consequences. Clicking the checkbox Stop displaying this dialog will reset the PrefShowLSHandlerRankDialog preference.