Hi All,

New Windows builds are now available at www.partha.com. Please see details at the website.

In particular, G'MIC 1.5.1.0 is now integrated into the Useful Plugins downloads and built into the portable versions.

Please let me know if you have any questions.

Thanks,
Partha

Thanks Partha!

Thanks Partha! You're irreplaceable !
The first little attention:
The first consideration when you start is an old problem (with Themes)
http://www.gimpchat.com/viewtopic.php?f=7&t=3387&start=40%20#%20p43224
In version Jernej Simončič http://www.gimpchat.com/viewtopic.php?f=7&t=3867%20#%20p47806 does not have this problem in the default installation (XP 32 bit)
Any suggestions?

Themes just do not work well with Gimp-2.7 versions.
Whole dialogs seem to vanish sometimes.

I do like the splash screen.

Graechan,

This is important feedback. Thanks! Can you tell me what happened when you clicked on it? Did you get any error message?

Partha

Unable to reply to Rod because of sql errors. I will try later. Anyway here is what I was posting:

Hi Rod,

I don't know why Ender's version does not have the issue since we are using the same gtk-2.0. Perhaps you can change the theme and it will work better? I left in the default so that you can change it what you like as opposed to what I like.

Is everything else working like tiff etc.?

Thanks for the feedback.
Partha

OK Thanks! Will you be able to test another version for me? I am testing it now and if you agree, I can send you the new gimprun.exe or you can download the latest version of the 32-bit portable build tomorrow.

Hi Partha.

Best. Great job. I have to compile Gimp by myself, because I need a little
modification regarding the paintbrush size. It functions great (with your guidance),
but my gimp-2.7.exe is over 27 MB in size. Do you know why?

Hatti

Hi Hatti,

I don't include debug information (-g) and then I run "strip -p" on the final exes. Did you do that?

Also, can you tell me what mods you make? Perhaps it's somethings the developers should know or consider or if it does not affect ordinary usage, i can build it in as well?

Thanks!
Partha

Hi Partha.

No, I didn't do that. Thanks for the info, I will try.

My modifications are the brush size of the paintbrush-tool.
I never use brushes with the size of 10000 an very seldom I use brushes up to 1000 in size.
So I modificated the maximum brush size to 1000 and limited the size slider from 1.0 to 100.0,
so I can better handle brushes of ~10-20 in size.
The sizes are hardcoded in the source, I hoped that there was a possibility to change the behavior
by modifying a .rc file, but unfortunately these modifications require a compilation.

Greets
Hatti

yes flexibility vs slider precision, a nasty issue or the range should be limited or the sliders tend to skip intermediate values and so lack precision and give problems with finetuning

Anyway there is a workaround :
instead than use sliders (or even the arrows close to sliders) just click on the slider to be sure it get focus
but then use the "<" and ">" computer arrows to modify the values (same if you manually insert number in the numeric box field )that allow to increase/decrease values with much more precision

This in general; works with almost any graphic software

in theory any hardcoded value may be easily transformed in a variable:

1 ) suppose the max brush size (or whatever ) has a hardcoded value of 10.000 and it is called
"MBS" (Max Brush Size)

2) let rename the hardcoded value of "MBS" as "HBS" (Hardcoded Brush Size)
"MBS" remain the name used to define the max brush size , that now become undefined as value,,we will define in next step

3) now..
MBS(max brush size) = HBS (hardcoded value) x Variable (where "Variable" is a user chosen floating value..let say from 0.01 to 10 )
the max brush size now may vary from 100 to 100.000 according to user setting
(i doubt that someone may need a 100.000 px brush even 10.000 seems far too large...but it was just a example)

Not sure how to apply in practice but in theory should work

@PhotoComix

Of course it would.
I defined

#define MIN_BRUSH_SIZE 1.0
#define MAX_BRUSH_SIZE 1000.0

and replaced the hardcoded values in the .c source.
But modifying .c source means recompiling.
The multiplier idea is great and I hope, that there will be
a preference option for it in the future.
I don't know C so much, and I don't know Gimp-C even lesser,
so I am not able to make a suggestion to the developers.

Hatti

Hatti,

Check the source for the author and submit a patch. Or better yet, file a bug report and attach a patch to that. These reports are reviewed by the team. They are usually very receptive to this.

Partha

Actually Partha i believe you are replying to MareroQ?
Anyways i fixed the extra comments.Sorry for the mishap.

Thanks for the correction, Rod. I was getting sql errors at the site last night.

the portable rocks !
You only should take care to not create preference path outside the gimportable folder
(open it: the .gimp-2.7 folder is the equivalent of the gimp user folder in the user directory of the normal version ) then you may customize as you wish and use from the main HD (that is my main use )or a pen-drive ...

Btw i am just adding your scripts...well it take a while because i hate extra menus (as "script fu") so i am modifying the registry paths