I second PC's request.

@lylejk - Unfortunately ofnuts is correct in that the main performance hit I get is because of the pixel sampling (as far as I know, sampling a drawable is slow, both in scheme and python). his script should be a little faster as he uses the histogram function to access the percentage covered for the entire image, which my script can'r do as it is varying the density based on the source map rather than being the same density over the entire image.

If you need a fixed density, his is definitely the one to use as it will be faster.

@offnuts - My experimenting with undo freeze/thaw has shown to me it should only be used on a new image, not the user's working image, as it borks u pthe undo history completely. I have made a few other scripts where I create a new image (never displayed) and copy of the desires source layers, freeze the undo stack on that image and process. This really improves performance. In the case of this script, I wanted to have the visible feedback of the script working so the fill appropriateness could be judged easier and the script aborted if necessary, rather than having to wait a (still) long time with the work being done in a hidden image. I should test and see the performance improvement though - it might be worth it.

Ideally, I should just write a C plugin and be done with it.

-Rob A>

My current version (not the on on SF) does:


and it seems to work fine for the undo.

I tried exactly that (wrapping the main loop of the script) in a freeze/thaw pair, and while it runs in 1/3 less time, Undo does nothing afterwards.... I wonder if this is a bug in scheme if it works in python...

-Rob A>

where would this reside within GIMP???

If you are asking about my script, it shows up under Filters/Render

Cross-checked my code and it works flawlessly with the undo/redo. I updated the SF version if you want to check it out. I doubt the problem is Scheme vs Python...

Thanks ofnuts...one can only hope...but I dont see it sadly
Some of the python filters show and some dont....

Mac OS X 10.6.8 if you are wondering.

If I try this with a brush that is NOT from the gimp install the script screams at me:

<type 'exceptions.IOError'>: [Errno 9] Bad file descriptor

*burp said Gimp*

If I try this with a brush that is NOT from the gimp install the script screams at me:

<type 'exceptions.IOError'>: [Errno 9] Bad file descriptor

*burp said Gimp*

I have python installed and other python scripts work find.

I have a lot of py filters that don't show up, but all the scm filters do show up and work fine. I wondered if it was because of osx and why py's would be so different from scm's.

Technically , Scheme scripts are plain files that are executed by the Scheme executor that itself behaves as a plugin. But the Python plugins behave like full-blown plugins, exactly as if they were compiled C. I don't know much about OSX, but a glance at Wikipedia tells me it handles file permissions the Unix way: this means that plugin executables (this includes the .py files in the plugin directory), should have the executable bit set. In Linux, those without that flag don't show up either.

gah, I have no idea how one sets an executable bit.

In Linux "chmod +x {file}" in the CLI, and in the graphical file explorers, usually somewhere in the right-click menu, the "properties" or "access control" or "permissions".

afaik, I do have admin. permission for everything on this computer...is that what you mean? It's all above my understanding.

He meant the individual file. Right click the file in the folder and check Properties, to see if it has been given permission, etc. Not sure how that works in a Mac.

on my mac I right click and then click on get info and it shows that it is not locked, and I have permissions to read and write. and it opens with python launcher app.

There was a lot of traffic in thread when I posted and it may have gotten over looked.

If I try this with a brush that is NOT from the gimp install the script screams at me:



*burp said Gimp*

I have python installed and other python scripts work fine, any ideas?

The error is strange because the script never deals with the brush file (all brush handling is done using the Gimp primitives). Post the brush somewhere or tell me where I can get it.

I use non default brushes with the script just fine.