Not sure how to title this question. I’m finding that sometimes after making changes to code in my applet, particularly in a script library, SD runs the applet as if the change was not made. For example, the change might be to add a variable that was not passed to a handler in a script library. Running the applet in SD causes the same error that the code change fixed. This is after compiling and saving both the script library and main.scpt.
I’ve found that if I quit SD and re-open my applet making no other changes, it runs successfully. Suggests that SD is running the old code.
This started with macOS Tahoe. Am currently running macOS 26.1 and Script Debugger 8.0.10.
Thanks. Sorry, I did search but didn’t find that topic. A couple more details:
I always recompile and save main.script – often make a minor change so it has something to compile.
I’ve noticed that SD often shows “Edited” at the top of the main window even though I’ve not made any changes, or have only changed code in a library. In that case, I don’t bother making a minor change, skip compiling and do a save.
I shut down and power off at the end of each day and cold boot every morning.
I’ve fairly sure closing and reopening the applet (and all open libraries) in SD doesn’t address the issue – some changes still seem to be not picked up.
I have two forms of the use script statement:
use run_Utilities_handlers : script “Utilities”
and
use script “Utilities2”
That’s a result of the history of developing the applet. I’m not sure this issue occurs with both forms.
macOS Tahoe has not been friendly to work on my applet. This is not a big concern.