Here’s a workaround, given it’s still not implemented.
GENERALIZED EXPLANATION
Batch Queue Manager implements custom shell scripts as tools.
Problem with it is that it doesn’t seem to understand Windows scripts.
You can get around this by simply making a Window script “wrapper” that opens file(s) in GIMP, and use that as the command in the digiKam script editor.
Another “get around” is that you probably should make the Windows script visible to the shell, i.e. the directory holding the script should be in your PATH environment variable, in order to avoid path delimiter interpretation issues.
STEPS
-
Choose a directory that holds your own Winodws scripts, such as batch files, PowerShell scripts, or other.
-
Make a script that opens files in GIMP, and save it in that directory.
for example
“C:\Program Files\GIMP 2\bin\gimp-2.8.exe” %1
2.1 Add the directory of the above script to the PATH variable,
by going to Control Panel/User Accounts, Change Enviroment Variables, and add the path to the PATH variable, e.g.
PATH;blablablabla;your-script-directory;
-
In the Batch Queue Editor, create a new Queue and/or Workflow, and put a “User Shell Script” in the tool list (it should be the only one there)
-
Type in the script editor
name-of-your-script $INPUT -
Save the Workflow, calling it something like OpenWithGIMP.
Note the absence of the quotes in the Batch Queue Manager script, and also in the Windows (batch) script where %1 is specified. No quotes means they are handled properly. (You will probably need the quotes around the GIMP executable path)
Done.