Bug 418426

Summary: Transformation mask does not respect opacity and blend mode settings for edited layer.
Product: [Applications] krita Reporter: karpi <karpi.web>
Component: Tools/TransformAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED INTENTIONAL    
Severity: normal CC: ahab.greybeard, griffinvalley
Priority: NOR    
Version First Reported In: 4.2.8   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description karpi 2020-03-03 12:53:27 UTC
SUMMARY

When using transformation mask with partially opacity set layer (ie 50% in my case), or layer with particular blend mode ("Soft light" in my case ) and edit it (ie changing its perspective in my case) 

- In the moment, when I try to edit it, opacity switches to 100% and blend mode switches to "normal"

- In the moment, when is editing finished, it switches back to 50% and Soft light.


So it is impossible to transform layer nondestructivelly with respect to underlaying context, like normal, destructive workflow does.


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT

Transformation mask should respect opacity and blend mode settings for edited layer.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Ahab Greybeard 2020-03-03 17:39:00 UTC
This does happen as described when using a transform mask.

(When using the transform tool on an image layer, the opacity setting is preseved during the operation but not the blending mode, which is 're-enabled' after the transform operation is completed.)

However, the opacity and blending mode effects are restored after any changes are made to the transform mask so the end result is non-destructive. It's only during the change to the transform mask that you lose sight of the details of the appearance of the final rendered result.
Comment 2 wolthera 2020-04-24 12:45:57 UTC
Yeah, this is a limitation of the preview, and we can do very little about it.. I am therefore going to close this bug.