… as defined for instance by the two calls Gimp.Procedure.add_palette_argument and Gimp.Procedure.add_palette_aux_argument?
Just “arguments” are actually in the PDB procedure API. So if I add a palette argument, when another plug-in runs this PDB procedure, they can actually set a palette in this arg.
“Auxiliary” arguments are not public, it’s an internal argument. You cannot set this arg when calling the procedure. It can be used for instance:
- For passing data from one call to another: good examples of this are the script-fu and Python console plug-ins which both have a “history” string array aux argument. As the name implies, they store the history of run commands, so that the next time you start one of these consoles, you can retrieve previously run commands (in previous calls, even after a restart of GIMP) with arrow keys. But this is not a public arg. You cannot call the consoles and override the history.
- For using the GUI-creation facility API: for instance, if I want to add some slider widget for something which I want in the GUI, but not in the PDB API, I could add an int aux argument. Then it would also be extra easy to pass this additional argument through functions without changing every private function’s signature (it would be accessible in reading and writing through the config object).
- For stuff which only makes sense when used interactively: say my plug-in has a preview with a zoom feature. I could have a floating point aux argument. But this is meaningless in the PDB API (it changes nothing in rendering).
- And so on.
1 Like
This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.