When a file is opened from the Finder, it is opened by the application that owns it. Therefore, since applications other than Script Debugger (such as Apple’s Script Editor) can claim ownership of script files, you might want to control the ownership of files created by Script Debugger.

To do so, go to the General preference pane and select from the Saving radio buttons.

• If you choose Script Debugger is always creator, any file saved by Script Debugger will have its creator code changed to Script Debugger.
• If you choose Keep original creator, creator codes of saved files not created by Script Debugger will be left untouched, but files created by Script Debugger will have Script Debugger’s creator code.
• If you choose No creator, any file saved by Script Debugger will have no creator code.

In theory, Mac OS X decides a file’s owner based on the internally stored creator code, if there is one; otherwise, it uses the filename extension (.scpt for a compiled script file, .scptd for a compiled script bundle, .applescript for a script text file). In reality, the interplay between these two modes of determining a file’s owner is somewhat unpredictable. Script Debugger offers the option to save files with no creator, thus forcing Mac OS X to fall back on the filename extension to determine ownership. Additionally, you can check Default editor for OSA scripts, applets and droplets in the General preference pane as a quick way of setting Script Debugger as the owner for files with the relevant filename extensions.