Re: [Gimp-developer] Gimp "make install" fails with undefined references to fresh-built gegl

[Carol Spears via gimp-developer-list]

On Tuesday, June 16, 2020, Charles Hymes  wrote:

> I built gimp 2.10.18 on CentOS 7 last year on another host, but on a new
> host with gimp 2.10.20, I'm stuck with undefined reference errors for GEGL.
> I'm not a c++ developer, so this is all a foreign language
>


No promises but, pretend it is 15 years ago and as root type 'ldconfig'.

Then try building GIMP again.

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] [Gimp-user] C2G

[Carol Spears via gimp-developer-list]

On Tuesday, June 25, 2019, Jack Ogden  wrote:

> Hi,
>
> I have been using the GEGL C2G a lot in Gimp 2.8. Now I have updated to
> 2.10 I find the parameters in Color to Grey very different and have been
> unable to get the same effects - they seem more washed out and with less
> contrast.
>
> Any thoughts?
>

I noticed this with linear desaturate and switched my scripts back to the
other sometime ago.

A better discussion of this might be found at the developer mail list where
the authors are more frequent.

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] When writing a GIMP Plugin using Python, can the Plugin display a GIMP based Dialog box informing the user if they haven't provided an argument?

[Carol Spears via gimp-developer-list]

On Wednesday, May 8, 2019, Craig Sanders via gimp-developer-list <
gimp-developer-list@gnome.org> wrote:

> Hello.
>
> I am writing a GIMP Plugin using Python, and this Plugin expects to receive
> a list of files as one of its arguments. My question is, if the user
> doesn't provide any files as arguments, can my Plugin display a GIMP based
> Dialog box informing them of this?
>

gimp.message(You did not provide files)

The message part should be in quotes probably
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Spyrogimp plugin rewrite

[Carol Spears via gimp-developer-list]

I just wanted to say that there are a lot of meanings to the phrase
"unmonitered email" and, I have been busy with other things and I am
sorry I missed this.  Looks like it might have picked up some spam.

On 10/21/18, Elad Shahar via gimp-developer-list
 wrote:
> Hi Jehan,
>
> For authorship, you can use the name and email as used on this mailing list.
>
> On Sat, Oct 20, 2018 at 12:15 PM Jehan Pagès 
> wrote:
>
>> Hi!
>>
>> On Sun, Oct 14, 2018 at 12:47 AM Elad Shahar  wrote:
>>
>>> Hi Jehan,
>>>
>>> Thanks for your feedback!
>>> The new version is here
>>>  .
>>>
>>
>> For the record, I saw the email and will review (and merge if no problems)
>> your code. I have had not much time this week, but hopefully it will be
>> better next week.
>> For git authorship, do you confirm I should use the name and email as used
>> on this mailing list?
>>
>> As for the GEGL operation discussion, I definitely see how cool it would
>> be.
>> But if you say it would remove some features, of course we could discuss
>> how to make the best out of both worlds. I don't know enough about this
>> plug-in yet to be 100% relevant though. :-)
>>
>> Here is what I have done:
>>>
>>> * I made "Esc" close the dialog (and cancel the pattern).
>>> * The issue with the broken icon was part of a larger issue that made the
>>> plugin look different than other plugins. This was resolved by using
>>> gimpui.py
>>> * I added a non-interactive API.
>>> * I made the dialog less tall, by grouping parameters in notebook tabs.
>>>
>>> In addition:
>>>
>>> * Using the "selection" shape now draws multiple shapes - if several
>>> paths were generated from the selection-to-path conversion.
>>> * Several new multi-sided shapes were added as fixed rings, with
>>> additional options.
>>>   These produce drawings similar to many guilloche patterns. Examples for
>>> the new shapes are here
>>> .
>>> * I added "long-gradient" support, that spreads across the entire
>>> pattern.
>>>   This was available in the previous spyrogimp.scm, and produces nice
>>> results which are difficult to obtain when trying to tune the gradient
>>> from
>>> tool settings.
>>> * Improved the speed of incremental drawing by using gobject.idle_add
>>> instead of timeouts.
>>>
>>> I'd be glad to fix any other issues.
>>>
>>> If the plugin is indeed updated in the repository, could I write
>>> documentation for the manual?
>>>
>>
>> You are more than welcome to contribute to the manual too. The source is
>> there: https://gitlab.gnome.org/GNOME/gimp-help
>>
>> Same as we welcome patches for GIMP, we also do welcome patches for the
>> manual. :-)
>>
>> Jehan
>>
>>
>>> Thanks!
>>> Elad
>>>
>>> On Sun, Sep 16, 2018 at 10:34 PM Jehan Pagès 
>>> wrote:
>>>
 Hi Elad,

 On Sat, Sep 15, 2018 at 4:14 PM Elad Shahar via gimp-developer-list <
 gimp-developer-list@gnome.org> wrote:

> Hi,
>
> Long ago, I have written a Spyrogimp plugin in scheme. The plugin is
> currently included in gimp (under Filters -> Render -> Spyrogimp). Now
> I
> have done a rewrite in python which I hope is a big improvement:
>
> * It provides immediate feedback, by incremental drawing to a temporary
> layer.
> * Supports using more tools to draw the pattern (e.g. stroke).
> * You can use a non-rectangular selection to serve as the shape of the
> "fixed ring". This is done by converting the selection to a path. If
> the
> path has more than one stroke, then a pattern is drawn only for one of
> them. ( I might improve that in the near future).
> * There is an additional way to specify the pattern, that is compatible
> with the notation in the toy kit Spirograph manuals.
> * Lots of tooltips
>
> If you want to try it, you can download it here:
> https://www.dropbox.com/s/r2t5o4n4kyvtkmi/spyro.py?dl=0


 That's a cool update, and we could replace the old spyro by the new one
 (or on 2.10 at least deprecate the old one and hide it from menus but
 leave
 it alongside for the PDB API).
 I wonder if this could not be a GEGL operation also by the way, rather
 than a plug-in.

 Feedback is welcome.
>

 * Would be nice that hitting "Esc" close the dialog (and cancel the
 pattern).
 * On my desktop (GNOME on Fedora 28), the dialog shows a broken icon.
 * The dialog is much too high. On my screen, part of it is out of screen
 (the buttons in particular) so I need to use the Super key + left mouse
 click trick to move the window. It would be nice to rearrange the
 buttons
 differently or hide a scrollbar.
 * Your new plug-in doesn't provide a non-interactive API as the old one
 used to. I think this would be quite needed to be able to replace the
 old
 plug-in correctly.

 Apart from these, that is a 

Re: [Gimp-developer] Errors in the new gimp version registering python scripts

[Carol Spears via gimp-developer-list]

On Sat, Jun 23, 2018 at 10:23 AM, Carol Spears 
wrote:

>
>
> On Sat, Jun 23, 2018 at 8:25 AM, Ofnuts  wrote:
>
>> On 06/19/18 21:43, Paco Garcia via gimp-developer-list wrote:
>>
>>> Is there any way to get more information about the gimp_wire_read ()
>>> error
>>> that occurs when loading python scripts? Many scripts that worked in
>>> previous versions of gimp fail in the new one without apparent cause.
>>> Spanish version:
>>> ¿Hay alguna forma de obtener mas información sobre el error
>>> gimp_wire_read() que se produce al cargar scripts de python?. Muchos
>>> scripts que funcionaban en versiones anteriores de gimp fallan en la
>>> nueva
>>> sin causa aparente.
>>> ___
>>>
>>
>> I have seen plenty of such errors and they don't make the registration
>> fail. In 2.10 for Windows, scripts that import pygtk can have problems (you
>> have to make sure you import gimpfu first). Would you have the URL to such
>> a script?
>>
>>
> That's right.  I've seen that error before though, but I write crappy
> python also.  Maybe it is missing its beginning:
>
> #!/usr/bin/env python
> # -*- coding: utf-8 -*-
>
> or pygtk is not installed.  Or maybe the script is a template and broken
> from the fill ins.
>
> My earlier suggestion to poke around with it was not wrong, however.
>

Maybe the file is base64 or whatever that format was for mail in the 1980s.

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Errors in the new gimp version registering python scripts

[Carol Spears via gimp-developer-list]

On Sat, Jun 23, 2018 at 8:25 AM, Ofnuts  wrote:

> On 06/19/18 21:43, Paco Garcia via gimp-developer-list wrote:
>
>> Is there any way to get more information about the gimp_wire_read () error
>> that occurs when loading python scripts? Many scripts that worked in
>> previous versions of gimp fail in the new one without apparent cause.
>> Spanish version:
>> ¿Hay alguna forma de obtener mas información sobre el error
>> gimp_wire_read() que se produce al cargar scripts de python?. Muchos
>> scripts que funcionaban en versiones anteriores de gimp fallan en la nueva
>> sin causa aparente.
>> ___
>>
>
> I have seen plenty of such errors and they don't make the registration
> fail. In 2.10 for Windows, scripts that import pygtk can have problems (you
> have to make sure you import gimpfu first). Would you have the URL to such
> a script?
>
>
That's right.  I've seen that error before though, but I write crappy
python also.  Maybe it is missing its beginning:

#!/usr/bin/env python
# -*- coding: utf-8 -*-

or pygtk is not installed.  Or maybe the script is a template and broken
from the fill ins.

My earlier suggestion to poke around with it was not wrong, however.

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Problems using the PF_STRINGARRAY parameter type when writing a Python plugin for Gimp.

[Carol Spears]

On Tue, May 22, 2018 at 8:17 PM, Craig Sanders  wrote:

> Hello.
>
> I'm trying to write a very basic plugin for Gimp using Python and I
> want its one and only parameter to be of type PF_STRINGARRAY. The goal
> of my plugin for the time being, is to receive a list of files, and
> then simply print their names on the Command line, when the plugin is
> run.
>

Huh. If I ever knew that PF_STRINGARRAY existed, it did not sink into the
gray matter much.

Try this, instead, perhaps.  It has the limitation of delivering all of the
files in the directory however:

Hmm, I have been doing this in two steps:

import os

def list_directory(directory):
cennotts = os.listdir(directory)
contents = sorted(cennotts)
return contents

def list_directory_ext(directory, ext):
total_contents = list_directory(directory)
contents = []
for content in total_contents:
if content.endswith(ext):contents.append(content)
return contents

They work with (PF_DIRNAME, "img_dir",   "Images directory", ""),

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] How to get color tag of layer in python plugin script?

[Carol Spears]

On Thu, Feb 22, 2018 at 11:06 PM, John Tapsell <johnf...@gmail.com> wrote:

> On 23 Feb 2018 10:57, "Carol Spears" <carol.spe...@gmail.com> wrote:
>
>
>
> On Thu, Feb 22, 2018 at 7:37 PM, John Tapsell <johnf...@gmail.com> wrote:
>
>> Thanks! It would be cool if it was a property on the layer itself in
>> python, and if there was a version that returned the actual colour name
>> instead of a number. (there isn't, right?)
>>
>> /Filers/Python Fu/Console has a browser button that gives a
> searchable list of what can be done.  I suggest that you search for "tag".
>
> Thanks - I don't see anything other than the get and set function, so I
> think this confirms that there is no method for getting the color tag as a
> string.  This is something that needs to be converted manually I think.
>

I was pleased to find that the new Layers Dialog is not just a pretty
face

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] How to get color tag of layer in python plugin script?

[Carol Spears]

On Thu, Feb 22, 2018 at 7:37 PM, John Tapsell  wrote:

> Thanks! It would be cool if it was a property on the layer itself in
> python, and if there was a version that returned the actual colour name
> instead of a number. (there isn't, right?)
>
> /Filers/Python Fu/Console has a browser button that gives a
searchable list of what can be done.  I suggest that you search for "tag".

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] How to get color tag of layer in python plugin script?

[Carol Spears]

On Wed, Feb 21, 2018 at 9:53 PM, Partha Bagchi  wrote:

> According to ./libgimp/gimpitem_pdb.c:879, gimp_item_get_color_tag gets
> the color tag of the specified item.
>
> Does that help?
>

 color_tag = pdb.gimp_item_get_color_tag(item)

I noticed that the layers dialog got really large.  Thanks for the pointer!

carol

___
>> gimp-developer-list mailing list
>> List address:gimp-developer-list@gnome.org
>> List membership: https://mail.gnome.org/mailman
>> /listinfo/gimp-developer-list
>> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>>
>
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] How to get color tag of layer in python plugin script?

[Carol Spears]

On Wed, Feb 21, 2018 at 9:16 PM, John Tapsell  wrote:

> Hi,
>
>   How can I get the color tag of a layer in a python plugin script please?
>
>
Not sure what you mean by "color tag" but the color picker can be invoked
with:
color = pdb.gimp_image_pick_color(image, drawable, x, y, sample_merged,
sample_average, average_radius)

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Colored Quick mask also to Grayscaled images

[Carol Spears]

On Sat, Nov 11, 2017 at 4:52 PM, Mario Sottile - Marionetas Mey <
mario...@gmail.com> wrote:

> Marionetas Mey
>
>> Just convert it to RGB.  Image->Mode->RGB
>>
> Yes, this is a workaround. My suggestion is to have colored Quick Mask
> also in Graycaled images without converting them. *This is the main issue.*
>

I am pretty sure that this is not "a workaround".  The surface of the image
when moded GRAY only has access to the gray colors.  So that gray that
quickmask adopts is the red that is set in the preferences.

If you are just making a selection, converting to RGB does nothing to the
original colors.  After the selection is made, set it back to GRAY and
everything is fine.

If I am wrong, and you have a patch for all of this you would like for GIMP
to do differently, it will go a lot farther than imagining things on the
developer list.

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] gcc-7 vs gcc-6

[Carol Spears]

On Sat, Nov 11, 2017 at 12:10 AM, Ken Moffat <zarniwh...@ntlworld.com>
wrote:

> On Fri, Nov 10, 2017 at 09:41:41PM -0500, Carol Spears wrote:
> >
> > I don't think I am the only person who has more than one version of gcc.
> >
>
>
> Certainly not, my point was that building a current package with two
> different versions of the compiler is unusual : most people install
> applications into /usr, a few prefer BSD-style /usr/local.  But to
> have both versions available you need to go out of your way to
> ensure that the first install is not overwritten by the second.
>
> According to the gcc releases list, the most recent release is gcc-5.
 https://www.gnu.org/software/gcc/releases.html

I think that the confusing thing is "gcc".  While "gcc" is what configure
looks for and uses, it does not actually exist.  It is a symbolic link to
one of the versioned binaries like gcc-4, gcc-5, etc. which easily can
and do fit into the same directory.  The symbolic link just points to the
version that gets used.

I think if you "ls -l /usr/bin/gcc" you will see the symbolic link.  Many of
the terminal emulators will highlight symbolic links in a different color
which
is nice for finding them without the additional ls option.

Symbolic links are so easy to make that the maintenance problem is on
the other side where it needs to be remembered.

I am deleting the g++ symbolic link all the time, for mostly political and
nefarious reasons.  It is easy enough to put it back when required and
I start to know the offensive and questionable software that uses it.

This is not the first compiler bug that shows itself on gimp, but it has
been a long while.

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Colored Quick mask also to Grayscaled images

[Carol Spears]

On Fri, Nov 10, 2017 at 10:20 PM, Laxminarayan Kamath 
wrote:

> my 2 Rupees:
>An option to change the mask to any hue we want would help.
> Additionally an option of automatic continuous slow rotation of the hue of
> the mask would help (in the same way marching ants help).
>
> You can change the color, via Preferences.

Don't you think that the fluid change that you are describing would be
distracting?

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] gcc-7 vs gcc-6

[Carol Spears]

On Fri, Nov 10, 2017 at 6:45 PM, Ken Moffat via gimp-developer-list <
gimp-developer-list@gnome.org> wrote:

> On Fri, Nov 10, 2017 at 04:52:43PM -0500, Elle Stone wrote:
> > On 11/10/2017 02:42 PM, Carol Spears wrote:
> > > After a couple of catastrophes, I reinstalled my operating system ...
> and
> > > eventually rebuilt gimp.
> > >
> > > The gcc-7 gimp failed to open with a
> > > gimp: symbol lookup error: gimp: undefined symbol:
> > > gimp_convert_dither_type_compat_get_type
> > >
> > > The gcc-6 gimp works fine.
> > >
> > > Were my problems related to gcc-7?
> >
> > In case it might be relevant, this bug indicates a problem specifically
> with
> > gcc-7.2:
> >
> > https://bugzilla.gnome.org/show_bug.cgi?id=787222#c5
> >
> > Best,
> > Elle
> >
>
> But if by 'rebuilding' Carol meant "recompiled on the same machine"
> I have no idea.  Her post implies that both gcc-6 and gcc-7 versions
> are on the same machine, which seems an uncommon approach (assuming
> both are the same version and this isn't just to test for gcc
> regressions).
>
> Same machine.  Same updated clone for years.

I was also compiling with gimp with gcc-7 successfully before my couple of
catastrophes, so I don't know why it would start to fail with the new os.

I was confused because I read something about compiler problems on
this list, but I wasn't having them.

==multiple compilers installed==
My software installer just announces that it is updating what it considers
to be "gcc", copies that binary into the directory of its choice and simply
ignores the previous gcc.  Compiler cruft!  When today started I had
gcc-4 from the installer and gcc-7 which I installed with the "real"
software.
I was thinking about getting gcc-5 just so I would have a complete set.

I am pretty sure that each new number of compiler is a new version,
hence the number.

I don't think I am the only person who has more than one version of gcc.

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] gcc-7 vs gcc-6

[Carol Spears]

On Fri, Nov 10, 2017 at 4:52 PM, Elle Stone <ellest...@ninedegreesbelow.com>
wrote:

> On 11/10/2017 02:42 PM, Carol Spears wrote:
>
>> After a couple of catastrophes, I reinstalled my operating system ... and
>> eventually rebuilt gimp.
>>
>> The gcc-7 gimp failed to open with a
>> gimp: symbol lookup error: gimp: undefined symbol:
>> gimp_convert_dither_type_compat_get_type
>>
>> The gcc-6 gimp works fine.
>>
>> Were my problems related to gcc-7?
>>
>
> In case it might be relevant, this bug indicates a problem specifically
> with gcc-7.2:
>
> https://bugzilla.gnome.org/show_bug.cgi?id=787222#c5
>
> That's a great screenshot at gcc!

   rm /usr/bin/gcc
   ln -s /usr/bin/gcc-6 /usr/bin/gcc

Is the "not fixing gcc" cure.

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

[Gimp-developer] gcc-7 vs gcc-6

[Carol Spears]

After a couple of catastrophes, I reinstalled my operating system ... and
eventually rebuilt gimp.

The gcc-7 gimp failed to open with a
   gimp: symbol lookup error: gimp: undefined symbol:
gimp_convert_dither_type_compat_get_type

The gcc-6 gimp works fine.

Were my problems related to gcc-7?

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Colored Quick mask also to Grayscaled images

[Carol Spears]

On Fri, Nov 10, 2017 at 9:02 AM, Mario Sottile - Marionetas Mey <
mario...@gmail.com> wrote:

> When I work with an grayscaled image (now, with x-ray photo), quick mask
> is also gray... it is almost invisible. In this case, I think it's more
> important to have it colored than with a colored photo!
>

Just convert it to RGB.  Image->Mode->RGB

You are right, btw, about it being important to use a color mask on a black
and white image.

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Gimp (git: 20171027) Free select tool does not select when the path is closed

[Carol Spears]

On Fri, Oct 27, 2017 at 8:54 AM, Gottfried Müller 
wrote:

> The selection is activated only after an activation "rectangle select
> tool" or "ellipse select tool".
>
> Or after you hit "Enter"
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Bug report in Levels control

[Carol Spears]

On Thu, Aug 31, 2017 at 10:44 PM, Ben Hutchinson  wrote:

> The Levels control (the dialog box you get with Ctrl+L) has a bug. When you
> select Value for the channel, it is supposed to have a histogram which is
> based on all of the color channels combined. However, this bug causes the
> Value channel for the histogram to only consider the green channel. The
> result is that when you select either Value or Green for the color channel,
> you get identical histograms. The levels sliders themselves work correctly.
> It's just the histogram that has the problem.
>
>
>
Early gimp (gimp-1.0.0 thru gimp-1.0.3 iirc) had some breakage on the red
channel.  You could start with a grayscale image, convert it to RGB and
using levels (at least, maybe other tools) change an image of blacks,
whites and grays to an image of reds.

Here is a tutorial that utilized this bug:
https://web.archive.org/web/20010107023700/http://at8.abo.fi:80/~mwikholm/com/gimp/tutor/glass/

I suspect that it has always been this way.

Let me know if you file a bug report about it.  This is just great!

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Bug report in Levels control

[Carol Spears]

On Thu, Aug 31, 2017 at 10:44 PM, Ben Hutchinson  wrote:

> The Levels control (the dialog box you get with Ctrl+L) has a bug. When you
> select Value for the channel, it is supposed to have a histogram which is
> based on all of the color channels combined. However, this bug causes the
> Value channel for the histogram to only consider the green channel. The
> result is that when you select either Value or Green for the color channel,
> you get identical histograms. The levels sliders themselves work correctly.
> It's just the histogram that has the problem.
>
> This bug is present in the latest beta/development version (at the time I
> wrote this email) of Gimp.
> That is version 2.9.4 commit 5afea2f
> Note that I'm using the Windows version of Gimp, not the Linux version (not
> sure if there are any differences between these 2 in functionality).
>

First, make sure you can reproduce it (ie, here it is the red channel, and
I never noticed that).

Second: https://bugzilla.gnome.org/enter_bug.cgi?product=GIMP
Perhaps attach a screenshot or not.  If you can figure out how to fix it,
patches for stuff like this are usually well received.

Also, this is kind of funny to me.  I wonder how far back this oddity goes.

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Painting on a text layer, turning it into a regular layer?

[Carol Spears]

On Mon, Aug 28, 2017 at 6:55 PM, Elle Stone 
wrote:

>
> I'm kind of hoping this is a bug and not the actually intended behavior.
>
>
The color can be changed via the text tool.

When I need to do things to a text layer that the text tool doesn't
understand, I make a copy of the layer when it is still a text layer.

Worse for me is that I cannot get rid of a large brush or any of the
transform tools or the pesky blend tool (all whose touch on an image is
cumbersome if not intended) quickly by touching the ruler and engaging the
move tool.  Downright inconvenient compared to older GIMP.

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] missing babl fast path and lt-gimp-2.9 segfault

[Carol Spears]

On Sun, Aug 6, 2017 at 7:00 PM, Carol Spears <carol.spe...@gmail.com> wrote:

>
>
>
> On Sun, Aug 6, 2017 at 5:30 PM, richard brown <richardbened...@gmail.com>
> wrote:
>
>>
>>
>> On 06/08/17 21:20, Carol Spears wrote:
>>
>>
>>
>> On Sun, Aug 6, 2017 at 1:49 PM, richard brown <richardbened...@gmail.com>
>> wrote:
>>
>>> No-one?
>>>
>>
>> Asking me?
>>
>> The babl fast path is probably not the problem, at least it is not a
>> problem here.  Actually, I kind of like it because I can watch it to know
>> where some of the other plug-ins are at in their progress.
>>
>> The last time I had a segfault like that, I was instructed to install gdb
>> (https://www.gnu.org/software/gdb/) because the regular stack trace is
>> not so helpful.
>>
>> That has been a few years now, so maybe my advice is outdated.
>>
>>
>> Thanks.  I tried it, and it doesn't like the "gimp-2.9" script that
>> launches the program.
>>
>> "/home/richard/Software/gimp-git/gimp/app/gimp-2.9": not in executable
>> format: File format not recognised
>>
>> gdb is going to want to be started from the command line.
>
> It is weird to me that you are running this from the source file.  You
> don't install into /usr/local or /opt or some such?  If you have been
> building and using gimp from there for a long while, that would not be the
> problem but I would have thought that this could cause problems, like gimp
> finding the plug-ins it brings, etc.
>
> Here is a how-to that doesn't mention anything I remember when I used gdb:
> http://web.eecs.umich.edu/~sugih/pointers/summary.html
>
> I remember using "bt"  something like 'gdb bt /path/to/binary/gimp-2.n'
>
> If you could get a good output from that, perhaps you could file a bug
> report and maybe the real hackers are there
>

After some thought, (and unfortunately no reading) I suspect that the "bt"
was typed during the stack trace.

Perhaps there is some reliable advice in the mail list archives

Carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] missing babl fast path and lt-gimp-2.9 segfault

[Carol Spears]

On Sun, Aug 6, 2017 at 5:30 PM, richard brown <richardbened...@gmail.com>
wrote:

>
>
> On 06/08/17 21:20, Carol Spears wrote:
>
>
>
> On Sun, Aug 6, 2017 at 1:49 PM, richard brown <richardbened...@gmail.com>
> wrote:
>
>> No-one?
>>
>
> Asking me?
>
> The babl fast path is probably not the problem, at least it is not a
> problem here.  Actually, I kind of like it because I can watch it to know
> where some of the other plug-ins are at in their progress.
>
> The last time I had a segfault like that, I was instructed to install gdb (
> https://www.gnu.org/software/gdb/) because the regular stack trace is not
> so helpful.
>
> That has been a few years now, so maybe my advice is outdated.
>
>
> Thanks.  I tried it, and it doesn't like the "gimp-2.9" script that
> launches the program.
>
> "/home/richard/Software/gimp-git/gimp/app/gimp-2.9": not in executable
> format: File format not recognised
>
> gdb is going to want to be started from the command line.

It is weird to me that you are running this from the source file.  You
don't install into /usr/local or /opt or some such?  If you have been
building and using gimp from there for a long while, that would not be the
problem but I would have thought that this could cause problems, like gimp
finding the plug-ins it brings, etc.

Here is a how-to that doesn't mention anything I remember when I used gdb:
http://web.eecs.umich.edu/~sugih/pointers/summary.html

I remember using "bt"  something like 'gdb bt /path/to/binary/gimp-2.n'

If you could get a good output from that, perhaps you could file a bug
report and maybe the real hackers are there

Carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] missing babl fast path and lt-gimp-2.9 segfault

[Carol Spears]

On Sun, Aug 6, 2017 at 1:49 PM, richard brown 
wrote:

> No-one?
>

Asking me?

The babl fast path is probably not the problem, at least it is not a
problem here.  Actually, I kind of like it because I can watch it to know
where some of the other plug-ins are at in their progress.

The last time I had a segfault like that, I was instructed to install gdb (
https://www.gnu.org/software/gdb/) because the regular stack trace is not
so helpful.

That has been a few years now, so maybe my advice is outdated.

Carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] GIMP git build error on Mac

[Carol Spears]

On Thu, Jun 1, 2017 at 7:15 PM, Partha Bagchi  wrote:

> Hi All,
>
> A new wrinkle since May 22 (my last build). Did a pull today and now I am
> now getting the following error on my Mac:
>
> GEN  xgen-bec
> > /bin/sh: -c: line 1: syntax error: unexpected end of file
> > make[2]: *** [gimpbaseenums.c] Error 2
> > make[1]: *** [all-recursive] Error 1
> > make: *** [all] Error 2
>
>
> 'git log' will tell you the commit numbers and developer notes.

'git log -p path/to/gimpbaseenums.c' will tell you the history of that
particular file.

The commit number will make it easier for people to look it up.  Even some
of the
current developers

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] question about script-fu and GIMP 2.10

[Carol Spears]

On Tue, May 30, 2017 at 2:18 AM, Marco Ciampa via gimp-developer-list <
gimp-developer-list@gnome.org> wrote:

> Hello dear devs!
> I was wondering if, when the GIMP version 2.10 is ready (BTW:
> forecast of the release date?) it will contain the old beloved
> script-fus with the file->button and file->logo menu entries.
> I am asking this because I use to compile an up-to-date dev
> version and I am not observing any menu entry of such.
>
> Perhaps there were some decisions about it that i missed?
>

I think this is the commit you are looking for:


commit 96ab6aa88e2d94241b7caba7f522afbde08ff36f
Author: Øyvind Kolås 
Date:   Thu May 3 03:47:05 2012 +0200

scripts: remove the entries registered in the create menu

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Problem with GIMP 2.9.x build dependencies

[Carol Spears]

On Thu, May 18, 2017 at 8:49 AM, Carmelo DrRaw  wrote:
> Dear GIMP experts,
>
> I am having troubles to compile the dependencies required to build the latest 
> GEGL/GIMP versions from GIT.
>
> The problem I am facing is the following:
>
> * on one hand, GEGL requires GLIB > 2.44.0
>
> * on the other hand, PyGTK (needed to have python support in GIMP) wants 
> pygobject-2.0, whose latest version I could find is 2.28.6

python-gtk2 contains pygobject now, for a while (if I remember
correctly).  I am using pygtk-2.24 and not having problems with it.

> Am I doing something wrong? Is there a recommended set of library versions 
> for compiling GIMP? Or should I patch object-introspection to add the missing 
> glib library?

Patch for gtk3?

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Please migrate to GitHub/CMake

[Carol Spears]

On Sun, May 7, 2017 at 4:07 PM, Liam R E Quin  wrote:

> Please remember that English is not the first language of everyone on
> this list, and people come from a wide range of cultures. I don't think
> Alexandre meant to be dismissive or rude with his "No" (and I think
> Carol's comment was meant ironically although I'm not certain).
>
Oh, in real, they truly concerned me.  AND they did make me cry at the
meeting about the web site, so it really depends on the day and the mood
for how much I agree they are jerks or not.

> On Sun, 2017-05-07 at 17:37 +0300, Alexandre Prokoudine wrote:
>> On Sun, May 7, 2017 at 5:06 PM, Shlomi Fish wrote:
>>
>> > I see some problems with GIMP development:
>> >
>> > 1. It's been taking too long to release new major versions.
>

Shlomi knows that it is taking the same amount of time that all the
others did.

I have been concerned because work seems to have stopped on
the gtk3 branch

> I build GIMP from git on my Mageia cauldron system. Yes, there are some
>  issues (I have to build gegl without video capture support for
> example, because there's no video device on my system since I don't
> have a camera) but if you have problems I'm happy to try & help.
>

I was told by one of the gimp-1.2 guys that Liam had joined the dark side.

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Please migrate to GitHub/CMake

[Carol Spears]

On Sun, May 7, 2017 at 8:04 AM, gregory grey  wrote:

> . There is plethora
> of other image editors, I can't see why I should not help someone else
> who knows better than behaving like a jerk.
>
Oh gosh, and they are so much worse in real life!!

carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] broken threshold

[Carol Spears]

My execution error is when I use gimp-drawable-desaturate and maybe it
is going to happen with gimp-drawable-select-color.

I suspect it is something in the enums.

When I was poking around within GIMP's py-enums, I noticed that there
was a change in them.  LUMINOSITY has changed to LUMINANCE.  I guess I
have been around a long while because I was told it was better to use
the "wordy" enum and not the number for scripting.

It was nice to see that threshold was fixed.  I was always uncertain
how to use the procedure command given how it is used via the gui.



On Mon, Nov 7, 2016 at 10:05 AM, Carol Spears <carol.spe...@gmail.com> wrote:
> gimp-context-set-sample-threshold and
> gimp-context-set-sample-threshold-int are giving me Execution Errors
> since commit 3307c719663dd3aefb5722ad5cdb7faf03bcfdaf
>
> It might be me.  I might have an int where a float is wanted.
>
> It might not be me though.
>
> Thanks, carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

[Gimp-developer] broken threshold

[Carol Spears]

gimp-context-set-sample-threshold and
gimp-context-set-sample-threshold-int are giving me Execution Errors
since commit 3307c719663dd3aefb5722ad5cdb7faf03bcfdaf

It might be me.  I might have an int where a float is wanted.

It might not be me though.

Thanks, carol
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list