Bug 389478

Summary: Transform tool edition on group layer ignores transform mask on children layers
Product: [Applications] krita Reporter: iszotic <iszotic>
Component: Tools/TransformAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: normal CC: andrew.crouthamel, griffinvalley
Priority: NOR Keywords: triaged
Version First Reported In: 3.3.3   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description iszotic 2018-01-26 19:20:50 UTC 
I'm trying to paint symmetric objects but the editions made with transform tool don't get carried on to the mirror part of the symmetric object. So I tried with a mirrored layer, but then when I try to move the layer and its mirrored clone simultaneously the mirror mask transform in the clone just breaks with tranform tool.

Steps

1) new document
2) create layer1, paint something
3) create clone1 of layer1, attach transform mask, make a flip, and translate to make a symmetric object
4) create group1 with layer1 and clone1
5) apply a tool transform on group1
6) the child transform mask on clone1 now has the transform made over the group ignoring their previous mask transform.

Workaround1

Move tool doesn't ignore the transform in child transform masks and recalculates correctly the child transform masks.

Workaround2

Locking the transform mask in child layers only works with masks with translation. masks with scaling(and flipping) or rotations break the group transformation made.

Workaround tried (fails)

Attach a second transform mask unlocked on child layers
Tick/Untick the work recursively button
Comment 1 iszotic 2018-01-26 19:49:27 UTC 
>_< sorry devs, I realize now that this is how transform tool should work because it works on selections, not layers. And transform masks only do a specific transform over a layer so it cannot have zones with different transforms. but still, un-interactive layer operations (rotation, scale) don't recalculate the transform masks.
Comment 2 wolthera 2018-01-28 15:47:29 UTC 
So... the report is instead:

"The operations in the layer->transform don't trigger transform mask recalculations"?

Because otherwise we can also just close this?
Comment 3 iszotic 2018-01-28 20:10:53 UTC 
(In reply to wolthera from comment #2)
> So... the report is instead:
> 
> "The operations in the layer->transform don't trigger transform mask
> recalculations"?
> 
> Because otherwise we can also just close this?

Yes that's the report now, do I have to make another report?
Comment 4 Andrew Crouthamel 2018-09-15 16:22:22 UTC 
(In reply to iszotic from comment #3)
> (In reply to wolthera from comment #2)
> > So... the report is instead:
> > 
> > "The operations in the layer->transform don't trigger transform mask
> > recalculations"?
> > 
> > Because otherwise we can also just close this?
> 
> Yes that's the report now, do I have to make another report?

Yes please. This keeps the reports clean and easy to understand for triagers and devs when they later review.