Gimp-2.7.4 comments

Rod · **Joined:** May 16, 2010 **Posts:** 14709 **Location:** USA

Please post them here.

PhotoComix · **Joined:** Apr 12, 2010 **Posts:** 5870

I posted in Help viewtopic.php?f=8&t=2647 because is not only for this version, BUT know the answer will help to use Gimp-2.7 with less hassles.when using script or plugin still working but not ported to the new API

Basically i wish to know how tell gimp in case of warning,(no to be applied to error messages , only for harmless warning) to shut up , instead then pop out the warning(s)

I believe JamesH wrote how to somewhere but the where seems hard to trace

MareroQ · **Posted:** Fri Sep 23, 2011 11:24 am **(#3)**

EXCELLENT !
I would like to remind you of a small problem:
http://www.gimpchat.com/viewtopic.php?f=7&t=2341#p30532
Also in 2.7.4

Rod · **Joined:** May 16, 2010 **Posts:** 14709 **Location:** USA

PhotoComix wrote:

I posted in Help viewtopic.php?f=8&t=2647 because is not only for this version, BUT know the answer will help to use Gimp-2.7 with less hassles.when using script or plugin still working but not ported to the new API

Basically i wish to know how tell gimp in case of warning,(no to be applied to error messages , only for harmless warning) to shut up , instead then pop out the warning(s)

I believe JamesH wrote how to somewhere but the where seems hard to trace

From the command window
-c, --console-messages
Do not popup dialog boxes on errors or warnings. Print the messages on the console instead.

partha · **Joined:** Mar 14, 2011 **Posts:** 998

Or open the error console from inside Gimp and then all warnings will go there and not clutter up the screen.

Rod · **Joined:** May 16, 2010 **Posts:** 14709 **Location:** USA

partha wrote:

Or open the error console from inside Gimp and then all warnings will go there and not clutter up the screen.

That is actually how i do it.

PhotoComix · **Joined:** Apr 12, 2010 **Posts:** 5870

Partha
I believe to have stumbled in a quite critical bug of the Portable build (only of the portable)

check your mail for details and how to replicate

partha · **Joined:** Mar 14, 2011 **Posts:** 998

PhotoComix wrote:

Partha
I believe to have stumbled in a quite critical bug of the Portable build (only of the portable)

check your mail for details and how to replicate

PC,

Saw your email and responded to it. I will definitely check it out.

Thanks,
Partha

gerard82 · **Posted:** Fri Sep 30, 2011 8:33 am **(#9)**

I installed Gimp-2.7.x from git on my regular install.
viewtopic.php?f=10&t=1261
I've done that before but I noticed interaction between 2.6 and 2.7.
So I installed 2.7 on a separate partition which of course will prevent any interaction.
However switching from one to the other becomes tedious to say the least.
After all the interaction is slight anyway.
The benefits are large: Lots of scripts and plugins for 2.6 don't work in 2.7.
When working in 2.7 and needing a script/plugin that refuses to work I save the file and then open it in 2.6.
For instance 2.7 refuses to accept the "xsane" plugin needed to get a scanned image into Gimp.
Gerard.

gerard82 · **Posted:** Sun Nov 20, 2011 11:22 am **(#10)**

I ended up installing Gimp from git on a separate partition.
Yesterday I compiled the latest version.
It failed because of this:

Quote:

21 hours Depend on lots of newer library versions Michael Natterer 4 -20/+21

It complained about gtk+ version needed upgrading.
I then installed gtk+-2.24.8-r1 instead of gtk+-2.24.5 but I got another error about glibc.
Upgraded that too.
Cairo and pango were also giving problems but using a Gentoo tool solved that.
Anyway it's running ok,gutenprint xsane and gmic plugins work.
http://git.gnome.org/browse/gimp/
If you compile from git you know what to expect.
Gerard.

Rod · **Joined:** May 16, 2010 **Posts:** 14709 **Location:** USA

Yes i think that was why my compile failed with TIFF libraries.Everything else works excellent you need only delete the 2 tiff plugins in the plug-ins folder. Of course you won't have any TIFF support in Gimp.

2-ton · **Posted:** Sun Nov 20, 2011 2:52 pm **(#12)**

I was playing with 2.7.3 today and found the single window was hard for me to get used to. I like being able to scoot the tool boxes and stuff around out of the way if I want.

Graechan · **Posted:** Sun Nov 20, 2011 5:32 pm **(#13)**

All Partha's builds except the portable 64bit one force a gimp restart on some scripts.

partha · **Joined:** Mar 14, 2011 **Posts:** 998

Graechan wrote:

All Partha's builds except the portable 64bit one force a gimp restart on some scripts.

Would you let me know which scripts are those? It may be inherent in those scripts.

Also, if the portable 64-bit does fine, it may be that you have something in your environment that is causing it. Note that the portable versions create their own environment and don't leave any footprints behind. Finally it may be a memory issue.

Graechan · **Posted:** Sun Nov 20, 2011 5:58 pm **(#15)**

Attachment:

2.7.zip [14.82 KiB]
Downloaded 53 times

Partha It's the texture-brickwall part of this script that I was trying to use, included is the image I had open.I then noticed it did same on JMS brickwall.

partha · **Joined:** Mar 14, 2011 **Posts:** 998

Graechan wrote:

Attachment:

2.7.zip

Partha It's the texture-brickwall part of this script that I was trying to use, included is the image I had open.I then noticed it did same on JMS brickwall.

Yes, you are right these scripts cause an error in msvcrt.dll.

However, these scripts were written for Gimp 1.2 and last updated in 2001. So, I am not sure they will work in this version. Sorry.

One user on Gimp registry suggested these as a replacement:
http://www.gimphelp.org/script24.shtml

HTH,
Partha

Graechan · **Posted:** Sun Nov 20, 2011 6:46 pm **(#17)**

Partha the script in question works in 2.6.11,2.7(james 32bit portable) and your 64bit-portable. But now its no longer usable or will 2.8 be more flexable.

PhotoComix · **Joined:** Apr 12, 2010 **Posts:** 5870

Maybe the previous warning now are becoming errors ?
I would try to apply the (previous )warnings to the script (usually is something simple as replace each
"gimp_image_add_layer" with "gimp_image_insert_layer"

that notepad++ and i suppose any other decent text editor may do automatically
(from "search" there is " search & replace")

"

partha · **Joined:** Mar 14, 2011 **Posts:** 998

Graechan wrote:

Partha the script in question works in 2.6.11,2.7(james 32bit portable) and your 64bit-portable. But now its no longer usable or will 2.8 be more flexable.

It's causing an error with one of Window's DLLs. That to me implies that there is some weird interaction that I cannot predict. Since my portables are self contained, it is possible that the error is avoided there.

It is also possible that James' portable is similar and 2.6.11 is quite old and was compiled awhile ago under different circumstances?

partha · **Joined:** Mar 14, 2011 **Posts:** 998

PhotoComix wrote:

Maybe the previous warning now are becoming errors ?
I would try to apply the (previous )warnings to the script (usually is something simple as replace each
"gimp_image_add_layer" with "gimp_image_insert_layer"

that notepad++ and i suppose any other decent text editor may do automatically
(from "search" there is " search & replace")

"

PC,

You are probably right. A combination of missing items which is resulting in a missing string and so strcmp () is causing a segmentation fault.

I will investigate and find out where the issues are.

Thanks,
Partha