Bug 379034 - Animation data is shared, not duplicated when duplicating a layer with frames
Summary: Animation data is shared, not duplicated when duplicating a layer with frames
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: Animation (show other bugs)
Version: 3.1.2
Platform: Other All
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2017-04-21 11:27 UTC by SirPigeonz
Modified: 2018-10-28 03:35 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
crash animation on duplicated layers (12.19 KB, text/plain)
2017-04-21 11:27 UTC, SirPigeonz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description SirPigeonz 2017-04-21 11:27:23 UTC
Created attachment 105127 [details]
crash animation on duplicated layers

Crash loggs in Attachement.

This one is really weird to reproduce:

1. Create new transparent layer
2. Draw on it
3. Ad new frame for it on timeline
4. Go to 2nd frame
5. Draw something on it
6. Duplicate Layer
7. On duplicated Layer change 2nd frame and move the frame to new position
8. On 1st Layer also move 2nd frame
9. You see that there is still frame on 2nd column
10. Delete that layer
11. Select other column/frame
12. Crash...
Comment 1 SirPigeonz 2017-04-21 11:34:30 UTC
New info.

When file is saved and reloaded. Crashing layer disappears BUT(!) duplicated layer 2nd frame that we moved to lets say 10th frame is moved to the same column that corresponding 2nd layer of original Layer is for example 3rd column...

I think that animation data is not properly duplicated when we duplicate layers and they use same data :/
Comment 2 Halla Rempt 2017-06-05 09:22:04 UTC
Yes, I think you're correct.
Comment 3 Halla Rempt 2017-06-05 09:28:07 UTC
Ah, please check 3.1.4 -- tyyppi says he's already fixed it for 3.1.3.
Comment 4 Halla Rempt 2017-06-05 09:28:20 UTC
Waiting for confirmation.
Comment 5 Andrew Crouthamel 2018-09-28 02:26:15 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-10-28 03:35:45 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!