That one worked. I note that the problematic CUSTOM-MODE reference appears to have been replaced by BLEND-CUSTOM, and NORMAL-MODE by LAYER-MODE-NORMAL as well.

Did you make the changes? If so, how (as in, in the world?) did you know what to change them to? I've had no luck finding references for these... whatever-they-are.

Also these scripts you've posted are v1.3, but there was a later version v1.4 which added the ability to get the starting value of the gradient by sampling the source at runtime.

I thank you.

Help>Procedure Browser. Type gimp-layer-get-mode in the search box. The correct mode syntax for scripting will be shown in the right hand window.

@gramp

Updating is just as Rod described, you should be ok using linux which has somewhat better tools than basic Windows when it comes to editing scripts.



Thanks for the reminder The Gimp 2.9 version was the first I came across in my archive. A bit further and I have the 1.4 version. Fixed same as before. attached.



This is it working and just for info Ofnuts has a couple of plugins for rendering along a path(s) not the same but you can get some nice effects.

@Rod Thanks. I had visited Help->Procedures, but went all-goofy when I got there and messed about looking for the Compleat List of Parameters (which is what I'll call CUSTOM-MODE and NORMAL-MODE). I did not recognize that the Function's the Thing in there.

I do think there ought to be a list of those Reserved Words somewhere, and ideally, a mapping of how they've evolved across versions.

@rich2005 Thanks for the hand up. I have tried hard to "collect everything Ofnuts ever wrote.", but I have been off-line for some months and expect/hope it has doubled.

@ofnuts Salami, salami, baloni.

@RMA Don't want to forget the reason my question was even askable. Paraphrasing the great philosopher, Yogi Berra, "Thank you for making this problem necessary."

@gramp
I am still wondering why the Gimp 2.9 version, which I pull out for use occasionally, works for me but not on your setup. The only thing I can think of is a Gimp compatibility switch --pdb-compat-mode on/off which AFAIK is normally on but might be off. Does not matter providing everything works

Looks like the RobA site is gone for good. You can still get the scripts via https://archive.org/web/ but might be worth someone making a copy of the files, for legacy purposes.

Is there an updated script for 2.10.32 gimp users who have windows systems?

I think I have posted this script here previously, and I am on Gimp 2.10.32 rev 1 and the script still works OK for me.

I saved all his scripts from his old site. I'll post them to gimpscripts.net under a new tab.

The Wayback link is up under the Old Archive tab on GimpScripts.net, I'll eventually load all the files to the server soon.

Another way is to:

- Define the two edges as paths
- Use my path-inbetweener to generate many intermediate paths (100, here)
- Use my ofn-stroke-fill-path to stroke each intermediate path using a color from a gradient



This is somewhat faster than RobA's technique because RobA script loops along the length of the path, painting gradients, while my technique loops across the width, painting uniform lines.

@ofnuts Your method would also seem not to require the starting and ending paths to have equal numbers of nodes, no?

I remind that RobA's approach (v1.4) admitted the possibility of telling the script to take the starting value of the gradient from whatever color lay under the current point on the beginning path (as contrasted with being the same fixed color).

That bit is key to heightmap-generator fanboys like me and pegleg44.

Cheers~

Unfortunately, path-inbetweener requires it so....

I pre-apologize for suggesting that path-in-betweener could be modified to adjust the fewer-noded path to have the same number as the more-noded one, before-hand.

Because as the great philosopher, Murphy, recorded among his famous Laws:
"Nothing is impossible for the one who will not be doing it."

Cheers, Of.

It could be modified, yes, it could be easily modified, less so.

Also the nodes tell the script what point in one path moves to what point in the other. In the example below, the bottom path is either linearly split to have its number nodes match the top path (what a script would do) or is split to somehow match the length division of the top path.



Remember that you can always add nodes to a path by Ctrl-clicking a segment