Hey @noisneil the macro is working great. Quick question: would it be possible to either remove the script text from the pasted action, or set that as an option? The pasted action still contains the script if you switch it from “Execute script file” to “Execute script text”, and removing the text would cut down on the macro size which is another benefit for macros with large/complex AppleScripts.
I've been hesitant to remove the text from the action, in case there's an issue (e.g. we accidentally overwrite the script file during macro testing) and we want to be able to access the text version again. Same reason I've been disabling rather than removing the original action.
What happens when we share a macro that relies on these external scripts and we've deleted the text version? It's all a bit anxious-making!
In an ideal world, it would convert every AppleScript action in the current macro. If you run it again it would convert them back. These functions could also be incorporated into our upload macro, checking for potential orphaned scripts before converting (and then converting back after upload if necessary).
If you run the macro with a script file version of the action selected, it will convert it back to a text version and tidy up your compiled scripts folder by deleting the script file and trashing its parent folders if they are empty.
The reason I've decided not to decompile and remove the text from the action is that a 10,000 character script takes up only 10KB, and I'd rather maintain that text as a backup in case a user's compiled scripts folder goes walkabout for some reason.
It also means that, when sharing macros, the recipient can switch the actions to use text and still have a working macro.