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 740313 - guillotine as option in knife tool
guillotine as option in knife tool
Status: RESOLVED DUPLICATE of bug 162257
Product: GIMP
Classification: Other
Component: Tools
2.8.14
Other All
: Normal enhancement
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2014-11-18 13:05 UTC by Jo
Modified: 2015-07-25 18:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jo 2014-11-18 13:05:09 UTC 
the guillotine option is a well known and useful command, why not integrate it into knife tool ?
Comment 1 Michael Schumacher 2015-04-03 16:25:23 UTC 
The knife tool is the crop tool, I guess?
Comment 2 Jo 2015-05-29 10:16:13 UTC 
(In reply to Michael Schumacher from comment #1)
> The knife tool is the crop tool, I guess?

affirmative.
Comment 3 Michael Schumacher 2015-07-20 11:43:14 UTC 
And how would that work?
Comment 4 Jo 2015-07-21 11:42:36 UTC 
(In reply to Michael Schumacher from comment #3)
> And how would that work?

the coming transformation tool for example, uses various features, so why not applying and simplifying other tools as well?
Comment 5 Michael Schumacher 2015-07-21 14:13:11 UTC 
What I want to know is how the guillotine is supposed to work in this case. What is the result that the user will get?
Comment 6 Jo 2015-07-24 14:04:18 UTC 
(In reply to Michael Schumacher from comment #5)
> What I want to know is how the guillotine is supposed to work in this case.
> What is the result that the user will get?

multiple (new) images parts from the whole image, like with the original tool. 
Dont know if multiple layers could be useful.
Comment 7 Michael Natterer 2015-07-25 18:10:21 UTC 
A proper slice tool is what we need, not some add-on to the crop tool.

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