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 452863 - Foreground selection tool behaves strangely when image not zoomed to 100%
Foreground selection tool behaves strangely when image not zoomed to 100%
Status: RESOLVED DUPLICATE of bug 448417
Product: GIMP
Classification: Other
Component: General
2.3.x
Other All
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2007-07-01 15:06 UTC by Michael Helwig
Modified: 2008-01-15 14:12 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Helwig 2007-07-01 15:06:23 UTC
Please describe the problem:
When an image is zoomed to any other size than 100% the foreground selection tool does not recognize the lasso-selected region when finished selecting but (randomly?) selects some other region in the image. This also happens when corrections are made to the (misplaced) selection by marking foreground or background. However, when applied to a picture zoomed to 100% everything works fine.

Steps to reproduce:
1. open some (jpg) picture
2. zoom it to 25 or 50 %
3. click on "foregorund selection tool"
4. Mark some area in the picture.




Actual results:
The area marked is not selected but some other area in the picture gets selected which hasn't been marked

Expected results:
It would be nice if the tool would select the area I actually mark and not some other part of the picture

Does this happen every time?
I could reproduce this with 3 jpeg-pictures different times, I didn't try more pictures up to now

Other information:
Using gimp-2.3.18. I'm not sure if the Python-Script extension works correctly on my machine (I don't think it does). The missbehaviour does not produce any special report when gimp is started from a terminal.
Comment 1 Michael Helwig 2007-07-01 15:10:40 UTC
I forgot to mention: My system is a recently updated Slackware-Linux 11 (nearly 12) system.
Comment 2 Michael Schumacher 2007-07-01 17:23:58 UTC

*** This bug has been marked as a duplicate of 448417 ***