https://bugs.kde.org/show_bug.cgi?id=428332

Dmitry Kazakov <dimul...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
      Latest Commit|                            |https://invent.kde.org/grap
                   |                            |hics/krita/commit/d6c78129b
                   |                            |feba8d608babe5e592226074a2f
                   |                            |75d7
             Status|ASSIGNED                    |RESOLVED

--- Comment #3 from Dmitry Kazakov <dimul...@gmail.com> ---
Git commit d6c78129bfeba8d608babe5e592226074a2f75d7 by Dmitry Kazakov.
Committed on 27/10/2020 at 21:09.
Pushed by dkazakov into branch 'krita/4.3'.

Fix loading masks with vector selections

Loading has become broken after commit from June 2020:
6f283ca981 Fix undo breakage after converting a pixel selecion into a vector
one

After this change, when a selection is converted into a vector form,
the content of the pixel selection becomes discarded (due to a separate
undo history). Theoreticalll, the projection should become updated using
KisUpdateSelectionJob, but it happens too lately (because the image is
locked while loading). More than that, this job doesn't cause a setDirty()
for the parental node. It happens because we don't usually expect vector
selections to be edited on anything other than selection masks (it is just
not possible for anything other than selection masks).

This patch fixes the issue by calling selection->updateProjection()
explicitly. That is not ideal, because it makes the projection
recalculated twice, but it doesn't seem to be too critical.

The patch also skips loading pixel selection at all, if any vector
selection is present. There is no need for it anymore.

M  +32   -10   plugins/impex/libkra/kis_kra_load_visitor.cpp

https://invent.kde.org/graphics/krita/commit/d6c78129bfeba8d608babe5e592226074a2f75d7

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to