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 712550 - Scissors tool forgets its selection
Scissors tool forgets its selection
Status: RESOLVED DUPLICATE of bug 767650
Product: GIMP
Classification: Other
Component: Tools
2.8.8
Other All
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2013-11-17 23:33 UTC by Wil Barath
Modified: 2016-11-07 18:29 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Wil Barath 2013-11-17 23:33:18 UTC
1) load an image into gimp

2) start making a selection with the scissors

3) when you get to the end of the selection, try to move the first point.  Hmm... okay so you can't move it... well if it's not in quite the right place you can always modify the selection later, right?

4) finish making the selection by closing it and clicking inside it.

5) Pretend that you just spent 1/2 hour carefully tracing a large and complex object, and you've found a small area you wish to remove from the selection - ry to create a new, negative selection by pressing the ctrl key and then using the scissors to cut out a portion of the existing selection.  

6) Poof, the initial selection disappears and is replaced by the portion you were trying to remove!

7) Reproduce the original outline again with the scissors, but this time don't click inside to convert it to a selection

8) It's impossible to select outside it to add to it.

9) Try using the square or circle tool to add or subtract from it.

10) Poof, your work is lost.  Check the undo/redo history - it never existed.
Comment 1 André Klapper 2013-11-18 11:33:20 UTC
Please try with 2.8.8 and report back.
Comment 2 Michael Schumacher 2013-11-18 12:33:22 UTC
Is this a duplicate of bug #345541?
Comment 3 Wil Barath 2013-11-18 15:59:18 UTC
It's related to #345541, but no, it's addressing a different bug.

#345541 addresses inconsistency in the behaviour of the scissors compared to any other selection tool.

Let me start by saying that not that long ago, The Gimp used to silently and irrevocably discard the selection if you clicked outside it.

We've come a long way in making The Gimp show a little more respect for the hard work its users put into using it... my bug report shows a way in which The Gimp shows a complete lack of regard for the work I put into making a selection, which took me back to the 1.x series.  It makes me grateful that selections are treated like real work - by being placed into the undo/redo history.  However, paths, which you'd think should be far more permanent than a selection... switch tools and *Poof*.  Gone.  No notice.  No way to get them back.

My personal opinion is that the Scissors tool should be a path generation tool, not a selection tool, and that once that path is complete we should have an option of using it as a selection border.  I mentioned that in the other bug report, which I came across while searching to make sure that I was not creating a duplicate.
Comment 4 Wil Barath 2013-11-18 19:33:25 UTC
Confirmed in 2.8.8

Repeat the steps to produce the bug:

1) open any image in the gimp.

2) choose the "intelligent scissors" tool

3) click 4 corners of a large square to produce a large selection but don't close it quite yet.

4) click to close it, but don't commit it to a selection.  It's visually both a closed selection, and a path.

5) switch to any other tool to try to either use that path as a path or to use that selection as a selection.  *poof* the path disappears, all work is lost, returning to the tool / undo / view history / nothing will recover it.
Comment 5 Michael Natterer 2016-11-07 18:29:33 UTC
Resolving as duplicate of a newer bug that has been fixed.

Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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