After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 704897 - fuzzy select - skip already selected regions
fuzzy select - skip already selected regions
Status: RESOLVED NOTABUG
Product: GIMP
Classification: Other
Component: Tools
unspecified
Other All
: Normal enhancement
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2013-07-25 22:54 UTC by Marc Weber
Modified: 2013-11-22 21:20 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
see this image to understand what I'm talking about (19.64 KB, image/png)
2013-07-25 23:34 UTC, Marc Weber
Details

Description Marc Weber 2013-07-25 22:54:55 UTC
The fuzzy select tool is nice - but annoying, because if you try to select something "nearby" whatever you already have selected the new area can go through the selected area and behind the selected area it can select additional pixels you don't want gimp to touch.

The fix is easy. add a [x] ignore selected pixels option and when selected
treat those pixels as no match.

Also adjusting the threshold or the channel to operate on is time consuming and tiresome - what about allowing the user to "draw a line marking a pixel region",
then try to determine the threshold and or channels which are very likely to match all those pixels - and then set the threshold automatically?

This way there would be a chance to simulate photoshop elements like selections - draw and be done.
Comment 1 Marc Weber 2013-07-25 23:34:05 UTC
Created attachment 250152 [details]
see this image to understand what I'm talking about

follow comments in image to understand the use case
Comment 2 Marc Weber 2013-07-25 23:48:47 UTC
additional idea: It would be fun to have more sophisticated ways to tell the fuzzy tool what should be a "no match", such as radius < N pixels from click position.

This way it could serve as smart brush like tool.
Comment 3 Michael Schumacher 2013-07-26 09:01:47 UTC
What is selected in the image you have attached?
Comment 4 Tobias Mueller 2013-11-22 08:53:39 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 5 Marc Weber 2013-11-22 13:06:52 UTC
For whatever reason I missed your comments.

On that image "nothing is selected", there is a guide how to understand what I'm asking for, and how to reproduce what I think should be improved.

1) select the "darker gray" border by using fuzzy select tool, nearby the one dot.

2) select "inner" nearby those two dots
Now the selection floats outside of the darker boarder.


I think there should be a way to prevent this, eg stop at selected pixels.
Comment 6 Max Mustermann 2013-11-22 14:28:05 UTC
Thank you, Mark, for your explanations. 
I could reproduce it. Anyway I don't think the tool behaves wrong: with the given parameters and starting point you will always select the whole image, because the contrast to the pixels at your starting point is within the threshold. With the given 'Replace selection' mode you always replace the selection - so the selection from the first step gets lost naturally.  
The easiest ways I could find to solve your problem are: 
- Only select the outer ring with a bit greater threshold to include the inner core in the selection. 
- Use the Threshold slider only to set an approximately suitable value. The 'paint' with the mouse/pen to the right or down to increase the selection or to the left/upwards to make it smaller (also see http://docs.gimp.org/2.8/en/gimp-tool-fuzzy-select.html). This works quite intuitively. 

I hope I could help you.
Comment 7 Marc Weber 2013-11-22 21:07:55 UTC
I didn't say "it behaves" wrong. I just ask you to think about adding a "new option" which would mean "while finding all nearby pixels matching the threshold" stop when hitting a pixel which already got selected.

I know how to work around it.But "Gimp" is the image manipulation app on linux.
And there have been use cases where this behavior described would have been very nice.

Thus in such use casing have an option like 'Select Transparent Areas' but which should be called 'don't select already selected pixels' would be nice.

This was not a help request "how do I get my job done", this was a feature request because I think it would be useful.

Of course you're the project members and you have to judge. I'm a user only.
Comment 8 Michael Natterer 2013-11-22 21:20:40 UTC
You have a point here. Could you present this idea on the gimp-developer
mailing list? We discuss new features there to get a wider audience.