Re: [Gimp-user] Feature request: Toolbox customisation
Quoting Kristjan Siimson : annoying distraction. I have never used Ink tool, and it is unlikely that I > ever will. Therefore, there should be a way to remove useless noise, a > feature TO ADD OR REMOVE TOOLS FROM TOOLBOX. take a look at windows\dockable\dialogs\tools you CAN turn or off any of the tools ver 2.6.3 ghk ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Feature request: Toolbox customisation
Kristjan Siimson (kristjan.siim...@gmail.com) wrote: > ever will. Therefore, there should be a way to remove useless noise, a > feature TO ADD OR REMOVE TOOLS FROM TOOLBOX. Shouting is not necessary - it is already there: File->Dialogs->Tools and then toggle the visibility with the "eye" icon. > Of course, one could go even further, make tool presets, add the ability to > move icons around, but for now that is not as important as getting GEGL > implemented. Reordering the tool list works as well. Bye. Simon -- si...@budig.de http://simon.budig.de/ ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
[Gimp-user] Feature request: Toolbox customisation
Hello, First of all, thank you for GIMP! I have a feature request. This has been bugging me for well over a year, yet only now I found my way around to the mailing lists. Currently, the toolbox features no more or less than 33 different tools. I don't remember the exact theory, but there is one that says that humans can't grasp more than 4 - 7 choices. Not sure about the number, and it is not important here, 33 is definitely much more than that. Most of the time when I do graphics work, I do not need 33 features. When I do pixel art, there are only a couple tools I need. Others are just an annoying distraction. I have never used Ink tool, and it is unlikely that I ever will. Therefore, there should be a way to remove useless noise, a feature TO ADD OR REMOVE TOOLS FROM TOOLBOX. Of course, one could go even further, make tool presets, add the ability to move icons around, but for now that is not as important as getting GEGL implemented. Sincerely, Kristjan Siimson ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
I wonder if a problem I have had with saving files from Gimp in Windows is somehow related. If I save direct to the local hard drive, there isn't much of a problem. But if I try to save to say, a flash drive plugged into the same computer running Gimp, or to a network drive, then file save times get really long. Yes, you expect those two situations to take a bit longer, but not that long. I can save an .xcf file to the local drive and then transfer it to a flash drive or a network drive and it is loads faster than trying to save directly from Gimp. (which is what I typically do, save first to the local hard drive, then transfer the file to the drive I actually want to store the file on.) --- On Sat, 1/3/09, Sven Neumann wrote: > From: Sven Neumann > Subject: Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog > To: "Heinrich Moser" > Cc: gimp-user@lists.xcf.berkeley.edu > Date: Saturday, January 3, 2009, 6:44 PM > Hi, > > On Sun, 2009-01-04 at 00:17 +0100, Heinrich Moser wrote: > > > Sven Neumann writes: > > > On Sat, 2009-01-03 at 17:35 +0100, Heinrich Moser > wrote: > > > > > >> Is it possible to make GIMP use the > "default" Windows File Open/Save > > >> dialog*, for example, by setting some secret > configuration option? > > > > > > No. And we are certainly not willing to add such > an option. > > > > OK, thanks for the information. In that case, I can > just hope that > > such a plug-in turns up again somewhere. > > You can easily write such a plug-in yourself, in case > there's really no > way to locate the old one. It should be a trivial plug-in > to write for > someone who knows the Windows file-chooser API. > > > > You should report this as a bug against GTK+ then > and perhaps you will > > > also want to help the GTK+ developers to isolate > and fix the cause for > > > this. > > > > Thanks for the pointer into the direction of GTK. To > verify this, I've > > just downloaded gedit. It seems to use the same file > open dialog > > library (except for the preview), but, surprisingly, > it is indeed > > faster than GIMP (~10 seconds to show the directory > contents, as > > compared to ~30 with GIMP). > > You should investigate this then. It seems rather unlikely > that GIMP is > doing something with the file-chooser that could be > responsible for > this. What GTK+ version are you using with GIMP and which > with gedit? > > Sven > > > ___ > Gimp-user mailing list > Gimp-user@lists.XCF.Berkeley.EDU > https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
Sven Neumann writes: > On Sun, 2009-01-04 at 00:17 +0100, Heinrich Moser wrote: >> Sven Neumann writes: >>> On Sat, 2009-01-03 at 17:35 +0100, Heinrich Moser wrote: Is it possible to make GIMP use the "default" Windows File Open/Save dialog*, for example, by setting some secret configuration option? >>> >>> No. And we are certainly not willing to add such an option. >> >> OK, thanks for the information. In that case, I can just hope that >> such a plug-in turns up again somewhere. > > You can easily write such a plug-in yourself, in case there's really no > way to locate the old one. Well, it was on registry.gimp.org until Dec. 2007 but, apparently, it has been removed: http://web.archive.org/web/*/http://registry.gimp.org/plugin?id=3908 > It should be a trivial plug-in to write for someone who knows the > Windows file-chooser API. Which is why I was surprised to hear that it's so difficult to add this feature. ;-) No, seriously, I fully understand Martin's points about maintainance. >>> You should report this as a bug against GTK+ then and perhaps you will >>> also want to help the GTK+ developers to isolate and fix the cause for >>> this. >> >> Thanks for the pointer into the direction of GTK. To verify this, I've >> just downloaded gedit. It seems to use the same file open dialog >> library (except for the preview), but, surprisingly, it is indeed >> faster than GIMP (~10 seconds to show the directory contents, as >> compared to ~30 with GIMP). > > You should investigate this then. It seems rather unlikely that GIMP is > doing something with the file-chooser that could be responsible for > this. What GTK+ version are you using with GIMP and which with gedit? I don't think I will further investigate this, since I don't see much point in this, to be honest. Yes, we could find out what's taking GIMP's file open dialog so long and make it be as "fast" as other GTK applications. But I really think the time is better spent solving the problem permanently (like implementing the above mentioned plug-in) rather than fine-tuning something that can never be as fast as the native OS implementation. Greetings, Heinzi ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
Hi, On Sun, 2009-01-04 at 00:17 +0100, Heinrich Moser wrote: > Sven Neumann writes: > > On Sat, 2009-01-03 at 17:35 +0100, Heinrich Moser wrote: > > > >> Is it possible to make GIMP use the "default" Windows File Open/Save > >> dialog*, for example, by setting some secret configuration option? > > > > No. And we are certainly not willing to add such an option. > > OK, thanks for the information. In that case, I can just hope that > such a plug-in turns up again somewhere. You can easily write such a plug-in yourself, in case there's really no way to locate the old one. It should be a trivial plug-in to write for someone who knows the Windows file-chooser API. > > You should report this as a bug against GTK+ then and perhaps you will > > also want to help the GTK+ developers to isolate and fix the cause for > > this. > > Thanks for the pointer into the direction of GTK. To verify this, I've > just downloaded gedit. It seems to use the same file open dialog > library (except for the preview), but, surprisingly, it is indeed > faster than GIMP (~10 seconds to show the directory contents, as > compared to ~30 with GIMP). You should investigate this then. It seems rather unlikely that GIMP is doing something with the file-chooser that could be responsible for this. What GTK+ version are you using with GIMP and which with gedit? Sven ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
[Gimp-user] Win32: Use standard Windows File Open/Save dialog
>I understand why it is the way it is, which is why I mention that it >is sometimes the 'right' decision. However, end users don't like it, >no matter what the technical merits may be. Also, each application >obviously has it's own special needs, and the OS default File Chooser >cannot satisfy them all. Maybe the GTK library (GtkFileChooser, to be specific) could show the native Windows dialog, if available? One standardised file chooser can't satify all needs, but a solution is that there are hooks and other mechanisms that allow applications to extend the file chooser. However this should be discussed in a GTK forum/mailing list. -- Richard H. ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
Hi! Sven Neumann writes: > On Sat, 2009-01-03 at 17:35 +0100, Heinrich Moser wrote: > >> Is it possible to make GIMP use the "default" Windows File Open/Save >> dialog*, for example, by setting some secret configuration option? > > No. And we are certainly not willing to add such an option. OK, thanks for the information. In that case, I can just hope that such a plug-in turns up again somewhere. >> The reason that I want this is because the GIMP dialogs are terribly >> slow when accessing a slow (e.g. VPN) UNC network path (= >> \\IP-Address\Share\directory\...). > > You should report this as a bug against GTK+ then and perhaps you will > also want to help the GTK+ developers to isolate and fix the cause for > this. Thanks for the pointer into the direction of GTK. To verify this, I've just downloaded gedit. It seems to use the same file open dialog library (except for the preview), but, surprisingly, it is indeed faster than GIMP (~10 seconds to show the directory contents, as compared to ~30 with GIMP). Greetings, Heinzi ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
2009/1/3 Martin Nordholts : >> There seems to be a NIH syndrome in many programs, Gimp included, >> where the devs feel (possibly rightly in many cases) that they must >> reimplement core OS functionality. > > Hi, > > GIMP not reimplementing core OS functionality, we are using the GTK+ > library so that we can care as little as possible about OS specific > things. Your point about inconsistent file choosers is still valid but I > don't really see a trivial solution. Keep in mind that GIMP's usage of > the file chooser is more involving than just firing up a dialog to get a > file path. It would not be feasible to maintain the code that interacts > with the file chooser for multiple file choosers, at least not with the > current GIMP developer resources. > > BR, > Martin > I understand why it is the way it is, which is why I mention that it is sometimes the 'right' decision. However, end users don't like it, no matter what the technical merits may be. Also, each application obviously has it's own special needs, and the OS default File Chooser cannot satisfy them all. -- Dotan Cohen http://what-is-what.com http://gibberish.co.il א-ב-ג-ד-ה-ו-ז-ח-ט-י-ך-כ-ל-ם-מ-ן-נ-ס-ע-ף-פ-ץ-צ-ק-ר-ש-ת ا-ب-ت-ث-ج-ح-خ-د-ذ-ر-ز-س-ش-ص-ض-ط-ظ-ع-غ-ف-ق-ك-ل-م-ن-ه-و-ي А-Б-В-Г-Д-Е-Ё-Ж-З-И-Й-К-Л-М-Н-О-П-Р-С-Т-У-Ф-Х-Ц-Ч-Ш-Щ-Ъ-Ы-Ь-Э-Ю-Я а-б-в-г-д-е-ё-ж-з-и-й-к-л-м-н-о-п-р-с-т-у-ф-х-ц-ч-ш-щ-ъ-ы-ь-э-ю-я ä-ö-ü-ß-Ä-Ö-Ü ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
Dotan Cohen wrote: > 2009/1/3 Heinrich Moser : > >> Is it possible to make GIMP use the "default" Windows File Open/Save >> dialog*, for example, by setting some secret configuration option? I >> remember that there was a plug-in for this a long time ago (which >> added "Windows Open" and "Windows Save As" menu options) but I cannot >> find that anymore. >> >> > > There seems to be a NIH syndrome in many programs, Gimp included, > where the devs feel (possibly rightly in many cases) that they must > reimplement core OS functionality. Hi, GIMP not reimplementing core OS functionality, we are using the GTK+ library so that we can care as little as possible about OS specific things. Your point about inconsistent file choosers is still valid but I don't really see a trivial solution. Keep in mind that GIMP's usage of the file chooser is more involving than just firing up a dialog to get a file path. It would not be feasible to maintain the code that interacts with the file chooser for multiple file choosers, at least not with the current GIMP developer resources. BR, Martin ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
2009/1/3 Heinrich Moser : > Is it possible to make GIMP use the "default" Windows File Open/Save > dialog*, for example, by setting some secret configuration option? I > remember that there was a plug-in for this a long time ago (which > added "Windows Open" and "Windows Save As" menu options) but I cannot > find that anymore. > There seems to be a NIH syndrome in many programs, Gimp included, where the devs feel (possibly rightly in many cases) that they must reimplement core OS functionality. File Chooser dialogs are among the most visible (and annoying) of these cases. Although you use Windows, here is my Kubuntu bug about the situation: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/281834 -- Dotan Cohen http://what-is-what.com http://gibberish.co.il א-ב-ג-ד-ה-ו-ז-ח-ט-י-ך-כ-ל-ם-מ-ן-נ-ס-ע-ף-פ-ץ-צ-ק-ר-ש-ת ا-ب-ت-ث-ج-ح-خ-د-ذ-ر-ز-س-ش-ص-ض-ط-ظ-ع-غ-ف-ق-ك-ل-م-ن-ه-و-ي А-Б-В-Г-Д-Е-Ё-Ж-З-И-Й-К-Л-М-Н-О-П-Р-С-Т-У-Ф-Х-Ц-Ч-Ш-Щ-Ъ-Ы-Ь-Э-Ю-Я а-б-в-г-д-е-ё-ж-з-и-й-к-л-м-н-о-п-р-с-т-у-ф-х-ц-ч-ш-щ-ъ-ы-ь-э-ю-я ä-ö-ü-ß-Ä-Ö-Ü ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Win32: Use standard Windows File Open/Save dialog
HI, On Sat, 2009-01-03 at 17:35 +0100, Heinrich Moser wrote: > Is it possible to make GIMP use the "default" Windows File Open/Save > dialog*, for example, by setting some secret configuration option? No. And we are certainly not willing to add such an option. > The reason that I want this is because the GIMP dialogs are terribly > slow when accessing a slow (e.g. VPN) UNC network path (= > \\IP-Address\Share\directory\...). You should report this as a bug against GTK+ then and perhaps you will also want to help the GTK+ developers to isolate and fix the cause for this. Sven ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] GIMP 2.6.4 RPMs for Fedora 10, and 8
Johan Vromans writes: > I've made a complete set of RPMs available for Fedora 10, and 8. These kits contain a build error due to a known bug (not mine). This bug could lead to Gimp crashes when trying to import PDF documents. Please use the corrected kits, with release "2jv", instead. DISCLAIMER: They work for me. Your mileage may vary. Fedora 10: Note that you don't need the devel and debuginfo RPMs for normal use. http://www.squirrel.nl/pub/xfer/gimp-2.6.4-2jv.fc10.i386.rpm http://www.squirrel.nl/pub/xfer/gimp-debuginfo-2.6.4-2jv.fc10.i386.rpm http://www.squirrel.nl/pub/xfer/gimp-devel-2.6.4-2jv.fc10.i386.rpm http://www.squirrel.nl/pub/xfer/gimp-libs-2.6.4-2jv.fc10.i386.rpm http://www.squirrel.nl/pub/xfer/gimp-help-browser-2.6.4-2jv.fc10.i386.rpm Fedora 10, Source RPMs: http://www.squirrel.nl/pub/xfer/gimp-2.6.4-2jv.fc10.src.rpm Fedora 8: Fedora 8 requires an update to GLib2, babl and gegl. WARNING: Installing the new glib2 will make it impossible to upgrade your Fedora kernel! This is a known bug (not mine). So before upgrading your Fedora kernel, downgrade glib2 to its original version! Note that you don't need the devel and debuginfo RPMs for normal use. http://www.squirrel.nl/pub/xfer/babl-0.0.22-1jv.fc8.i386.rpm http://www.squirrel.nl/pub/xfer/babl-debuginfo-0.0.22-1jv.fc8.i386.rpm http://www.squirrel.nl/pub/xfer/babl-devel-0.0.22-1jv.fc8.i386.rpm http://www.squirrel.nl/pub/xfer/gegl-0.0.18-1jv.fc8.i386.rpm http://www.squirrel.nl/pub/xfer/gegl-debuginfo-0.0.18-1jv.fc8.i386.rpm http://www.squirrel.nl/pub/xfer/gegl-devel-0.0.18-1jv.fc8.i386.rpm http://www.squirrel.nl/pub/xfer/gimp-2.6.4-2jv.fc8.i386.rpm http://www.squirrel.nl/pub/xfer/gimp-debuginfo-2.6.4-2jv.fc8.i386.rpm http://www.squirrel.nl/pub/xfer/gimp-devel-2.6.4-2jv.fc8.i386.rpm http://www.squirrel.nl/pub/xfer/gimp-libs-2.6.4-2jv.fc8.i386.rpm http://www.squirrel.nl/pub/xfer/gimp-help-browser-2.6.4-2jv.fc8.i386.rpm http://www.squirrel.nl/pub/xfer/glib2-2.18.2-1jv.fc8.i386.rpm http://www.squirrel.nl/pub/xfer/glib2-debuginfo-2.18.2-1jv.fc8.i386.rpm http://www.squirrel.nl/pub/xfer/glib2-devel-2.18.2-1jv.fc8.i386.rpm http://www.squirrel.nl/pub/xfer/glib2-static-2.18.2-1jv.fc8.i386.rpm Fedora 8, Source RPMs: http://www.squirrel.nl/pub/xfer/babl-0.0.22-1jv.fc8.src.rpm http://www.squirrel.nl/pub/xfer/gegl-0.0.18-1jv.fc8.src.rpm http://www.squirrel.nl/pub/xfer/gimp-2.6.4-2jv.fc8.src.rpm http://www.squirrel.nl/pub/xfer/glib2-2.18.2-1jv.fc8.src.rpm Happy gimping, -- Johan ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
[Gimp-user] Win32: Use standard Windows File Open/Save dialog
Hi! Short question: Is it possible to make GIMP use the "default" Windows File Open/Save dialog*, for example, by setting some secret configuration option? I remember that there was a plug-in for this a long time ago (which added "Windows Open" and "Windows Save As" menu options) but I cannot find that anymore. Long explanation (i.e. why would I want this): The reason that I want this is because the GIMP dialogs are terribly slow when accessing a slow (e.g. VPN) UNC network path (= \\IP-Address\Share\directory\...). For comparison: After choosing a directory, GIMP takes ~20-40 seconds before showing the contents (the dialog being unresponsive during that time). On the other hand, Thunderbird (to use another multi-platform open-source product for comparison) pops up the default Vista file save dialog, which shows the directory contents almost instantly. I'm not sure if this is a GIMP bug or not; it's quite possible that Microsoft is doing some behind-the-scenes magic here (caching, undocumented functions, whatever) that causes it to be a whole lot faster than any other "custom-made" file chooser implementation. I'm using a workaround currently (putting the network directory in "offline mode" before using GIMP, which causes the UNC share to be redirected to a local cache directory; and synchronizing afterwards), but I really wish I wouldn't have to. Greetings, TIA, Heinzi * e.g. by using the GetOpenFileName/GetSaveFileName API functions ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] 2.6.4 crashes on PDF import
Sven Neumann writes: > Since there have been no changes in the GIMP code that could explain > this, you should have a look at the build process. Looks like you did > not build the poppler plug-in. I verified the crashes with the Fedora 10 version of Gimp 2.6.3. The Fedora version does not use the poppler plugin for PDF import, although it mentions poppler-devel with the build requirements. It uses a ghostscipt plugin instead. This plugin crashes on specific imports. It turns out to be a missing requirement. The build needs poppler-devel AND poppler-glib-devel. The latter is not listed with the build requirements. I'll file a bug report with Fedora, and rebuild my kits. Thanks for pointing me into the right direction. -- Johan ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] 2.6.4 crashes on PDF import
Hi, On Sat, 2009-01-03 at 15:04 +0100, Johan Vromans wrote: > I get crashes with 2.6.4 when trying to import a page from a PDF > document. This happens on Fedora 10 and 8. It doesn't happen with > 2.6.3. > > As a start, I noticed a different PDF import dialog[1]. 2.6.3 shows > thumbnails of all PDF pages, 2.6.4 shows a simple dialog where to > enter the resolution and the page number. When I do this, I get the > following error: > > Calling error for procedure 'gimp-image-undo-enable': > Procedure 'gimp-image-undo-enable' has been called with an invalid > ID for argument 'image'. Most likely a plug-in is trying to work on > an image that doesn't exist any longer. > > Opening '/home/jv/tmp/week01.pdf' failed: PDF document plug-In could > not open image > > Any hints where to start looking? Since there have been no changes in the GIMP code that could explain this, you should have a look at the build process. Looks like you did not build the poppler plug-in. Sven ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
[Gimp-user] 2.6.4 crashes on PDF import
Hi, I get crashes with 2.6.4 when trying to import a page from a PDF document. This happens on Fedora 10 and 8. It doesn't happen with 2.6.3. As a start, I noticed a different PDF import dialog[1]. 2.6.3 shows thumbnails of all PDF pages, 2.6.4 shows a simple dialog where to enter the resolution and the page number. When I do this, I get the following error: Calling error for procedure 'gimp-image-undo-enable': Procedure 'gimp-image-undo-enable' has been called with an invalid ID for argument 'image'. Most likely a plug-in is trying to work on an image that doesn't exist any longer. Opening '/home/jv/tmp/week01.pdf' failed: PDF document plug-In could not open image Any hints where to start looking? -- Johan [1] Note that this could be caused by a change in build spec. For 2.6.3 I used the Fedora 8 build spec, for 2.6.4 I used the Fedora 10 build spec. ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Foreground Select Tool
Owen wrote: > Selecting the Foreground Select Tool gives me the 'lasso' (Free Select > Tool) tip and it acts as the Free Select Tool, not as the Foreground > Select Tool Hi, The Foreground Select Tool is based on the Free Select Tool and you are supposed to select the initial area using the Free Select Tool logic. Refer to the (not updated for 2.6) documentation: http://docs.gimp.org/en/gimp-tool-foreground-select.html BR, Martin ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
