A known GIMP issue is the selection view. If you do ctrl T, it disables this and any plugin that runs with a selection will be 3 to 5 times faster (including yours). The caveate is you won't be able to see your selection. Not a programmer, but if you can do ctrl T before your script runs and then do ctrl T to re-enable selection view, you may be very happy with the boosted speed. :)
Didn't know that, so just tried. But I only see a small improvement (about 5%) in cases where it really counts (very thick rims, 200 pixels for instance). This is coherent with a comment made by one of the main Gimp developers. In fact minimizing the window while the script runs us even more efficient...
quote "I was thinking about making a single, curved line path. You can't make that a selection."
1 add a new transparent layer
1 there stroke the path with a 1 pixel brush and a solid color (i.e. black)
3 select the black (or if the BG is transparent Layer/transparency/alpha to selection )
Well you can always add a couple of points, make a selection, and cut off the excess rendering... Not always pretty or practical, I agree.
Under the hood WrapMap uses the selection a lot. To draw against a path, a completely different method would be used (hopefully also a lot more efficient).
Comments
Fixed in 0.3
A bit more difficult than expected :-)
New version 0.2
Just uploaded version 0.2 to SourceForge. Just performance improvements, 10-20% faster, and uses only half the memory. Enjoy.
A known GIMP issue is the
A known GIMP issue is the selection view. If you do ctrl T, it disables this and any plugin that runs with a selection will be 3 to 5 times faster (including yours). The caveate is you won't be able to see your selection. Not a programmer, but if you can do ctrl T before your script runs and then do ctrl T to re-enable selection view, you may be very happy with the boosted speed. :)
Disabling selection view
Didn't know that, so just tried. But I only see a small improvement (about 5%) in cases where it really counts (very thick rims, 200 pixels for instance). This is coherent with a comment made by one of the main Gimp developers. In fact minimizing the window while the script runs us even more efficient...
Never tried minimizing while
Never tried minimizing while running a plugin before. Thanks for the info. :)
Map to Path?
It would be a nice addition.
I've always wanted to be able to make a gradient follow a path for a rainbow and this works for that.
I went outside the image boundary to make a path so that only the part that crossed the image was visible.
I can't make the image show in here. Just click the link to view the image.
http://gimpchat.com/files/53_rbow_ldscp.jpg
Mapping to path
It's easy to transform a a path into a selection, so creating an intense double rainbow is a Small Matter Of Gimping:
(OTOH real rainbows are circular so a selection would be better)
Mapping to Path
I was thinking about making a single, curved line path. You can't make that a selection. Mapping to the path would work in that instance.
quote "I was thinking about
quote "I was thinking about making a single, curved line path. You can't make that a selection."
1 add a new transparent layer
1 there stroke the path with a 1 pixel brush and a solid color (i.e. black)
3 select the black (or if the BG is transparent Layer/transparency/alpha to selection )
Mapping to Path
Well you can always add a couple of points, make a selection, and cut off the excess rendering... Not always pretty or practical, I agree.
Under the hood WrapMap uses the selection a lot. To draw against a path, a completely different method would be used (hopefully also a lot more efficient).
Pages