https://bugs.kde.org/show_bug.cgi?id=476776
Dmitry Kazakov <dimul...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INTENTIONAL
Status|REPORTED |RESOLVED
--- Comment #6 from Dmitry Kazakov <dimul...@gmail.com> ---
Hi, Dorijan!
The key point is this one:
> 3. Select layer with Free Transform tool and attempt to move it around,
> performance will be fine at first, then resize, rotate or something (don't
> resize too small or it won't be noticeable as much) and apply transform.
When you first activate a transform tool and try to move the layer, it does
**not** do the transformation. It behaves as a move tool, i.e. just offsets the
layer. As soon as you perform any real transformation action (like, rotation or
scale), this fast-path optimization goes away and Krita starts to perform a
fully-featured transformation, which is slow, since it starts to juggle with
actual pixels.
And, yes, this behavior does not go away until you perform any **undoable**
action. In your example you add/remove layers, which is an undoable action and
resets the "continued" mode.
I don't think we can do anything about it. Raster transformations are slow. And
we have a fast-path only for the non-transformed clips. That is the bug is not
actually "performance drop", but "performance is too fast on activation of the
tool" :)
--
You are receiving this mail because:
You are watching all bug changes.
