Bug 438342

Summary: Animation curves - Transform Mask - New keyframe
Product: [Applications] krita Reporter: grum999
Component: AnimationAssignee: Eoin O'Neill <eoinoneill1991>
Status: RESOLVED DUPLICATE    
Severity: normal CC: eoinoneill1991, tamtamy.tymona
Priority: NOR Keywords: release_blocker
Version: nightly build (please specify the git hash!)   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:

Description grum999 2021-06-09 17:31:17 UTC 
SUMMARY

More detailed information on krita-artist.org
https://krita-artists.org/t/krita-5-animation-curves-applied-to-transform-mask/24895/1#animation-curves-transform-mask-new-keyframe-9

STEPS TO REPRODUCE
1) Create a paint layer with a rectangle
2) Add a transform mask on paint layer
3) Create first keyframe at frame 0
4) Move to another frame (example, frame 15)
5) Select “Transform tool”
6) Click on layer


OBSERVED RESULT
For the second keyframe, created automatically when transform tool is applied to layer, value are incorrect:

- No transformation is applied
-  Curves defines a transformation

If we move to another frame, the right values are applied to curves


EXPECTED RESULTS
When a new keyframe is created without transformation, curves should represent the right values.

SOFTWARE/OS VERSIONS
Linux appimage krita-5.0.0-prealpha-dba5ce5-x86_64.appimage

Grum999
Comment 1 Eoin O'Neill 2021-06-10 00:30:29 UTC 
Confirming this, but it isn't always consistently the wrong value.

Likely has to do with threading issues.
Comment 2 Eoin O'Neill 2021-06-24 02:26:03 UTC 
This is a duplicate of the issue found in 438917 -- if we solve one, it will solve both...

*** This bug has been marked as a duplicate of bug 438917 ***
Comment 3 grum999 2021-06-24 06:18:27 UTC 
(In reply to Eoin O'Neill from comment #2)
> This is a duplicate of the issue found in 438917 -- if we solve one, it will
> solve both...
> 
> *** This bug has been marked as a duplicate of bug 438917 ***
From a developer point of view, maybe

From a user point of view, that's not the same case.
I'll wait for bug 438917 being fixed :)


Grum999