Page 1 of 1

It would be nice if a transformation's original state was cached, to speed up a cancel operation.

Posted: April 20th, 2022, 11:52 am
by jfoster
It would be nice if a transformation's original state was cached, to speed up a cancel operation.
Now, when using Edit Transformation to check something (maybe saving a mask out as a file) or trying something new, when you Cancel the transformation often a full recalc is invoked.

In particular, the Precise Gaussian Blur can be very time consuming on a Cancel. A fast roll-back on a Cancel would improve the user experience imho.


Jeff

Re: It would be nice if a transformation's original state was cached, to speed up a cancel operation.

Posted: April 26th, 2022, 4:51 pm
by jsachs
This sounds like it's worth doing for several of the transformations that tend to be slow (Precise Gaussian, Multipass Sharpen, etc.). For most transformations, making an extra copy of the output image may not speed things up appreciably and it takes extra memory.

Re: It would be nice if a transformation's original state was cached, to speed up a cancel operation.

Posted: April 28th, 2022, 8:53 am
by jfoster
As you say, no need to speed up already fast cancels.

I did some other prodding related to the PGB Cancel and found that if you cancel the Precise Gaussian Blur progress when the transformation is opened to Edit Transformation, the Cancel does not return to the original state. Rather, the null from the cancelled progress bar persists.

Jeff