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

            Bug ID: 458471
           Summary: Locking/Unlocking layer generate an update of layer
                    stack
           Product: krita
           Version: 5.1.0
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Layer Stack
          Assignee: krita-bugs-n...@kde.org
          Reporter: grum...@grum.fr
  Target Milestone: ---

SUMMARY
In synthesis, if filter mask/transform mask is attached to a layer, lock/unlock
action on layer and/or mask will generate an update of layer.

A more detailed an readable summary is available on krita-artists
(https://krita-artists.org/t/locking-unlocking-layer-does-it-need-to-recompute-everything/46462/8?u=grum999)
There's different case/combination where it's possible to reproduce the problem
(really not easy to write/provide clear explanation without text formatting
here :-) )

Also note on krita-artists topice, there's 2 problem (this one and another one
related to performance: problem about performance will be reported in an
another bug report)


STEPS TO REPRODUCE
Describe only the first case of 7 described on krita-artists
1.  Create a new document (a large one 7000x5000 help to see better the
problem)
2.  Fill paint layer
3.  Add a transform mask and edit it ("mesh transform" help to see better the
problem, but problem occurs with any transform mode)
4a. Lock/Unlock paint layer and/or transform mask
4b. Alphalock/Alphaunlock paint layer

OBSERVED RESULT
Layer is updated (flickering canvas + update progress bar in status bar)


EXPECTED RESULT
Lock/Unlock shouldn't have an impact on canvas refresh

SOFTWARE/OS VERSIONS
  Build ABI: x86_64-little_endian-lp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: linux
  Kernel Version: 4.19.0-21-amd64
  Pretty Productname: Debian GNU/Linux 10 (buster)
  Product Type: debian
  Product Version: 10
  Desktop: KDE

ADDITIONAL INFORMATION
>From python scripting
```
from krita import *

d=Krita.instance().activeDocument()
n=d.activeNode()
n.setLocked(not n.locked() )
# n.setAlphaLocked(not n.alphaLocked() )
```
We can see that update is not triggered

Problem seems to be related to action made from user interface only:
- modify value from layer stack 
- from layer stack when access to layer properties [F3] and change property,
problem occurs too

Tested on Krita 4.2.8, 4.2.9, 4.3.0, 4.4.8, 5.0.6, 5.1.0, 5.2.0a
-> problem start to occurs from Krita 4.3.0

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

Reply via email to