rickk Wrote:(03-28-2021, 12:35 PM)Krikor Wrote: If there is only one selection, and not a path (no stroke), I think this message would be expected (Brush strokes on path Warning
'NoneType' object has no attribute 'strokes'), as the plug-in is expected to be applied to paths rather than selections.
You're right, my comment was intended as an observation only, not a critique.
But, here is the odd thing that I noticed. After failure on the selection ellipse, I did an "undo" to blank canvas...then plotted a path, and successfully stroked it with Of-nuts script. Same path several times with different brushes. Then, I did an undo back to a blank canvas (and it was definitely blank) I replotted a selection ellipse, and again tried to stroke it with of nuts' utility.
This time, no error message, but the brush strokes would only plot on the portion of the erased path falling inside the new selection ellipse.
So, despite being undone to the point of invisibility, the path still existed in zombie form. and accepted the brush strokes inside the selected area. Not really so much a problem, as it was a curiosity.
A bug report is a statement of fact, not a critique. There are several thousands bug reports against Gimp, you have to assume that the developers don't take that personally
My fix was mostly replacing a cryptic error message from the Python interpreter by a slightly more useful one.For your "problem": when you create a path, it is marked as not visible by default so your path was still there. Then if you still have a selection when you apply the script, the strokes are constrained to the selection as usual. So I assume you undid up to the point where you just created a path from the selection, which is when you have both the selection and the not visible path.