Thank you very much, Dinasset. There are so many nice scripts here to play with! I wish I had more time to play with all of them and learn more.

Pat and Issabella:

I feel that looking at your images made with this script is a really very relaxing and calming viewing experience. Almost like a therapy thread for the busy.

Thank you so much Skinnyhouse.

I'm still learning to manage this script.

The first and the third ones are interesting from a graphical viewpoint, but IMHO implemented with wrong colours.

Still experimenting. After making my paths, did path blend with selected gradient, then used Replicate in Rings.

Pat, that is really nice and innovative.

Thank you very much Issabella. With this one I had 2 paths of spades, then used copy, rotate nLayer.scm on it. Then used the same gradient for the background in a different manner.

Very good your last one, Pat.

Thank you, Dinasset.

Didn't see a PM - did it get worked out?

-Rob A>

RobA, I have the problem of not knowing what the overlap function is, or how to use it. I played with the slider but did not notice any changes. What am I doing wrong?

It is really subtle. With an overlap of 0 you will usually end up with semi-transparent gaps between each stroke, or a moire pattern. Top is 0, middle is 1, bottom is 2



With the default (1) it is usually fin, but depending on the ratio of the paths or their orientation there may still be gaps, so you can dial it up to 2.

It is a question of speed versus quality, as it makes more strokes, closer together when it is at 1 or 2.

Thank you for the information. I did not know what it did or what to do with it. Now I can play with it.

You can create such objects in Inkscape and then export the finished product to PNG.
1. Create a small triangle, and copy it to clipboard
2. Using the bezier curve tool, at the top of the program (somewhere) there should be a dropdown, "Shape" set to "From clipboard"
3. Set Mode to create spiro paths
Things you draw, will look like such objects as the one on clipboard. Now, coloring is a different story. Sure, Inkscape does have gradient fill, but will it work in this case? Maybe one of the newer versions have more settings.
The attachment shows the finished thing, it consists of two objects (convert the bezier curve with Path > "Object to path" to create an object we can use), split by a rendered line made from the object itself and then adjusted to fit in the middle of it. Both objects (spiro and line) were duplicated, on one pari I used Path > Difference on, and the other Path > Intersection. Then I joined them together and exported the image.
Clear as mud? Ask!
HTH

I've been away too long. (I have been trying to protect the plate while dealing with a steady stream of curveballs. Curveballs is probably a bad metaphor as most of the situations I've been dealing with were self-actuated, like felling a 70-ft tree across a shed and seeing my pickup break in half from lack of undercarriage care.)

Part of my absence stems from an extended downtime of my CNC machine's control computer, but I was recently successful in installing a replacement, leading me back to GIMP use after 19 months... :shocked: That length of time away has worked a predictable loss of memory about how I used to do things. Slowly, slowly, I'm recovering some use of my faculties.

I came to this particular thread to review because of my heavy reliance on Path-Blend to generate smooth transitions in heightmaps, and I'm encountering an error (in GIMP 2.10) I have not seen before, or seen mentioned in the thread.

Following my workflow, I've created a simple path around an object, then duplicated that path, to ensure both paths have the same numbers of nodes. and then enlarged the second path by dragging nodes away from the first's. Finally, I ran PathBlend with a simple FG-to-BG gradient using the two paths.

I got an abort with this error:
Error: ( : 1) eval: unbound variable: CUSTOM-MODE

Reading back through the thread, it seems I was something of a cogniscento minore earlier on, but I can barely identify with that guy today.

I see lines like:
(gimp-edit-blend inLayer CUSTOM-MODE NORMAL-MODE GRADIENT-LINEAR 100 0 REPEAT-NONE FALSE TRUE 3 0.2 TRUE x3 y3 xQ yQ)
in the script, and do not see, for example, CUSTOM-MODE defined, so guess that it's something to be inherited from GIMP.

It is only a guess, but it seems possible that something has changed between v2.8 I used then and v2.10 now.

Anyone recognize the error, thanks?

I should add that I am running the apt install version of GIMP in Ubuntu 20.04, as contrasted with the snap install version. (The former suffers from Ubuntu having dropped Python2 support, and gimp-python, as I recall. The latter suffers from exceptional difficulty in opening project files that are, of course, stored outside snapcraft's favored "sandbox.")

I was able to get the former to work by following rich2005's guidance, which link I cannot now lay hands on, which involved adding a few more pkgs, including one called python-is-python2, as I recall, to fool too-clever Ubuntu 20.04 as I guess.

[EDIT: found the link to rich2005's advice which I followed:
https://www.gimp-forum.net/Thread-Heal- ... 4#pid18354
/EDIT]

I am having problems posting ? Ah -working now.

Try this one, works here kubuntu 20.04 / Gimp 2.10.32 remember to unzip it It is script-fu put it in your scripts folder.

see later post

@rich2005, thanks.
That one gives the same result: "Error: ( : 1) eval: unbound variable: CUSTOM-MODE"

On further investigation:
Edit->Preferences: Folders: Scripts
lists two paths:
/usr/share/gimp/2.0/scripts/
~/.config/GIMP/2.10/scripts/

This may mean nothing, but I notice that variable, or parameter, CUSTOM-MODE appears--only--in scripts in the my GIMP profile directory, where scripts have been gathered over time (an copied into this directory most likely from earlier GIMP versions). CUSTOM-MODE does not appear in--any--scripts in the global share directory. To me it feels like older scripts written based on expectations that have been supplanted.

Strange how that one worked for me, however it was an old fix for a between Gimp 2.8 & Gimp 2.10

Only a couple of lines to update. Try this one.



I would check that you do not have an old version somewhere in your setup.