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 784478 - Cage transformation very slow
Cage transformation very slow
Status: RESOLVED INCOMPLETE
Product: GIMP
Classification: Other
Component: Tools
2.8.22
Other Mac OS
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2017-07-03 14:39 UTC by Jo
Modified: 2017-10-17 21:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jo 2017-07-03 14:39:19 UTC 
The cage transformation tool was never quick, unfortunately. I have to wait at least 15 seconds after closing the path, and when i move any anchor point, also 10 seconds each time. 
Would be a fantastic tool :(
Comment 1 Jo 2017-07-03 14:43:19 UTC 
Correction: moving anchor points uses more than 20 seconds and Gimp is irresponsive/locked in that time
Comment 2 Jo 2017-07-03 14:57:06 UTC 
if the transformation with the cage tool isnt possible in real time, then let us:
- drag the anchor points as we desire
- hit enter to confirm the anchor point position, (for the transformation)
Comment 3 Michael Schumacher 2017-07-03 18:48:36 UTC 
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 757581 ***
Comment 4 Michael Natterer 2017-07-03 20:59:17 UTC 
Cage transform has nothing to do with perspective.
Comment 5 Michael Natterer 2017-07-12 07:51:47 UTC 
I think it's quite a bit faster on master.

Can you attach an xcf, with a selection of roughly what you would transform,
and tell us how long the two steps take for you?
Comment 6 Michael Schumacher 2017-10-17 21:29:19 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!