(07-02-2025, 12:34 PM)Frenchie Wrote: IYou write:
"For a simple procedure, you can run a scm as a plugin (in its own folder) starting with a shebang #!/usr/bin/env gimp-script-fu-interpreter-3.0"
Do you mean that in this case, there's no need to close Gimp and reopen it each time I make a change?
I ran a test: the change isn't taken into account if you don't close Gimp.
Depends on where the change it, as I said.
- In the script-fu server, scripts files are read once for all when the server starts, or when you asked it to refresh the scripts.
- In a plugin, the code file is read:
- On Gimp startup (if new or more recent than on previous startup) to create the registration entry in pluginrc , set-up menus, add to PDB with prrper arguments, etc...
- On each execution
So if the file is new (or in a a new location), and you change the registration part (menu entry, arguments, etc...) then yes you have to restart Gimp to have it taken in account, because this updates the
pluginrc file. But other changes in the code (i.e., those you do when you debug) are automatically taken in account when you execute. Of course at the beginning coming up with proper registration code may require several tries, and so several Gimp startups. But once this is done debugging/enhancing the code is smooth sailing.
