Multi-Fill Script Help

[akky]

I really like that stained glass one...

[akky]

oops...I think I put my post in the wrong thread ...meant it for the patchwork one

[akky]

Where did you put the patterns folder mahvin??? I just had ago at this but I went off to shower and when I came back it ws still seemingly filling with random patterns...I know not from whence but obviously the thing had crashed...perhaps because I didnt have anything in a patterns folder maybe......I've just rebooted GIMP and trying again but I fear the same thing is going to happen. LOL

[mahvin]

I made my own Patterns folder (I use this script to test glass textures with my stained glass patterns). So I created a Parent pattern folder (you can put this anywhere you want) and put various sub-folders with different glass colors and textures for testing. You HAVE to point the script to your particular pattern folder, it will not find it automatically on its own. Also, I didn't name my folders "Patterns" because I wanted to avoid confusion, so mine are named after the glass textures instead.

[akky]

ok I'll try that thanks Mahvin
I'm assuming they are jpg

[mahvin]

png and jpg

[Graechan]

Here are 2 off my images, 1 using patterns, and 1 using gradients

Patterns from one of my gurn folders

Using random gradients

to get the result from gradient choices I slightly modified the script

[Graechan]

Gurm is a very good program for storing your additional brushes, patterns, gradients, and palettes

it's another great program from RobA Available here

[Graechan]

This is the modified Flatting Tools script that I used

Flatting Tools with modified gradient options↓

FlattingTools.scm

(16.07 KiB) Downloaded 132 times

[dinasset]

Multi-fill called on an image with transparent areas goes into an endless loop.
To double-check:
-call script Pursuit Curve, with default parameters
-the result is a drawing with black lines on a transparent area
-now call Multi-fill, with default parameters
.......endless loop.....
please help, thanks!

[dinasset]

IMO, a script should, when called using default parameters:
- either work with acceptable results
- or notify with a message or something else that the base image is not acceptable
Thanks

[dinasset]

I used the available topic which says "...help", but in fact I was trying to notify what -IMO- there is a missing piece in the script, either to take care also of the transparent areas or to inform the user about the requirement to have NO transparent areas in the base image.
Hopefully RobA will sooner or later read this post...

[dinasset]

Yes, the script is very nice, I agree, it just needs some...clever interventions!

[Odinbc]

Multi-fill called on an image with transparent areas goes into an endless loop.
To double-check:
-call script Pursuit Curve, with default parameters
-the result is a drawing with black lines on a transparent area
-now call Multi-fill, with default parameters
.......endless loop.....
please help, thanks!

I see what you mean about the MultiFill endless loop, an error message the script couldn't proceed would have been helpful. Once I forced the shutdown of the MultiFill script I had to re-start Gimp because of various lost menu functions. This was when I ran Pursuit Curve, with default parameters. It seems Pursuit Curve need one of the Polygon fill options to work with MultiFill.

[dinasset]

just another indication about the script:
if I choose for Fill Type option 5 or 6 (gradient...)
the script at the end works, but I get a lot of this messages "Unable to run GimpPdbProgress callback. The corresponding plug-in may have crashed."

edit: even if I comment out all the lines related to "progress" (?)

edit 2: it only happens with the drawing created with the Pursuit Curve (having added a white layer below and flatting the image, to have the areas all white, as I do for any other option of Fill Type, otherwise none works as stated in a previous post)
if I just create a new white image and draw with a pencil various black lines, I do not get those messages...

[dinasset]

@odinbc
because I feel myself uncomfortable with having the mentioned messages show up only with the draw created with the Pursuit and not with a draw hand made by myself, I did a lot of experiment, increasing at each run the complexity of the drawing, and eventually I got the same messages about GimpPdbProgress callback also using my drawing.
I don't understand whether this happens because of the number of areas or the too many different area sizes, anyhow I attach here the original drawing and the filled one (result is always OK); if you both can experiment trying to multi-fill my original with option gradient, let me know your results, thanks.

draw.png (6.77 KiB) Viewed 1800 times

draw-filled.png (98.6 KiB) Viewed 1800 times

[Odinbc]

Two examples, one of each gradient fill option, with similar results to yours.



The same Gimp error message each run of MultiFill with gradient option on your image.

GIMP Error
Unable to run GimpPdbProgress callback. The corresponding plug-in may have crashed.

GIMP Error
Unable to run GimpPdbProgress callback. The corresponding plug-in may have crashed.

GIMP Error
Unable to run GimpPdbProgress callback. The corresponding plug-in may have crashed.

Gimp 2.8.6, Win32, MultiFill

[dinasset]

thanks odinbc!
does someone know when and why gimp issues those messages?

[Rod]

IMO, a script should, when called using default parameters:
- either work with acceptable results
- or notify with a message or something else that the base image is not acceptable
Thanks

It does work correctly if you follow the directions of the multifill script.

Multifill takes every background coloured space (selectable) and will fill them with sequential palette entries, or randomly. It does NOT check to see if adjacent colours are the same, but use of a large palette should reduce the likelihood.

It simply isn't designed to work with transparency.

[dinasset]

Rod,
I'm not expert enough on scripts to know whether is it possible to understand (by code statements, I mean) the presence of transparent areas in the base image/layer:
1 - IF YES, when a script not only ignores those areas (which is acceptable), but is going into an endless loop if they are present (causing GIMP to be forced closed -see experience of odinbc in addition to mine), then IT SHOULD REFUSE to execute issuing a warning message
2 - IF NOT, it could be nice for the users to see a warning on top of the parameters windows informing "this script is unable to deal with transparent areas" or similar