neurolurker wrote:
Dear Friends in the Distance, I'm using GIMP 2.10.10 on Windows 10. I've often had issues running many of Dinasset's Python scripts. I _believe_ but I certainly don't know for sure, that the problem might be that the Python initializing string:
#!/usr/bin/env python
does not appear as the first line in the script, but only after an explanatory comment block above the main script.
In both of the above examples, neither showed up in the menus until I cut the initializing string and pasted it at the top of the script file. Both versions then showed up in the menus and the QT210 version worked fine. [I also downloaded the DopeCrystals04seamless.jpg and put it in the patterns folder.] For whatever reason, the first version [in Wallace's post] gives the following error: "File "C:\Program Files\GIMP 2\- TRIAGE\DIEGO_Mosaic_Stained_Glass.py", line 567, in Mosaic_Stained_Glass
pdb.plug_in_gmic(newImage, Preprocessed_Layer, 1, # 1=input only active layer
error: procedure not found"." ["TRIAGE" is my try-it-and-see-if-it-works folder for new scripts.]
I don't know whether my experience with the "#!/usr/bin/env python" line has been the result of a problem with GIMP or scripting or Python or Windows 10 or something else. [A deep echoing voice in my head says, "No, Neurolurker, it's only a problem for you ... "] From the other users in the many previous messages about Dinasset's fantastic scripts, it was very clear that the plugins worked for them without issues, and so far as I recall, no other user mentioned it.
Exactly what i had to do to get Bytes and Pixels filters to work as well.
Word Art
Vector Path
Animated Brush
Spirograph
Glossy Web Button
Simple Button
All now work after adding the Python initializing string.