Bug 441150 - Storyboard Docker Bug - Frame number is not updated on moving to new frame- Krita 5.0 Beta
Summary: Storyboard Docker Bug - Frame number is not updated on moving to new frame- K...
Status: CONFIRMED
Alias: None
Product: krita
Classification: Applications
Component: Storyboard (other bugs)
Version First Reported In: 5.0.0-beta1
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-08-19 02:21 UTC by LaTor
Modified: 2021-10-20 21:31 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Recording of the Bug in Storyboard Docker (1.16 MB, video/webm)
2021-08-19 02:21 UTC, LaTor
Details

Note You need to log in before you can comment on or make changes to this bug.
Description LaTor 2021-08-19 02:21:31 UTC
Created attachment 140827 [details]
Recording of the Bug in Storyboard Docker

SUMMARY
When I create a panel in the storyboard docker and draw, it works perfect; however, when I move the corresponding keyframe in the timeline docker to a new frame number, it does not update the new frame number in the storyboard docker (number next to “scene 2” in the upper left-hand corner of the panel). This causes that when I click on the panel in the storyboard docker, it takes me to the original frame when the panel was created, not to the updated frame.

STEPS TO REPRODUCE
1. Click the "+" to add a new panel in the Storyboard Docker
2. In the Animation Timeline Docker, move the corresponding keyframe to a new location.
3. Click on the panel in the Storyboard Docker

OBSERVED RESULT
It will take to the frame number where the panel was originally created. 

EXPECTED RESULT
It should take you the updated frame number.

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

ADDITIONAL INFORMATION
I have attached a video recording of the bug.
Comment 1 Wojtek Trybus 2021-08-22 14:14:55 UTC
I'd like to confirm this bug. It's not windows specific - I replicated it on Kubuntu.

Timeline integration works well only from docker -> timeline, but not the other way round - It's possible to move elements on the timeline by changing amount of frames in the docker, but dragging those frames causes wrong storyboard elements to move (the frame length is changed not on a previous frame, but on the dragged one, causing mismatch).
Comment 2 Eoin O'Neill 2021-10-20 21:31:58 UTC
I've moved this over to the Storyboarding section and assigned it to me.

I think the appropriate short-term solution here will be to check the other layers after a keyframe is moved to determine if it's the last keyframe moved, and if so, determine whether...

1) The storyboard entry should be removed and the timing of the prior scene should be extended.
2) The storyboard entry's starting frame should be relocated to another "starting frame" with a new duration and the previous duration needs to be changed.
3) If the frame is being moved within a specific scenes length, we need to determine whether the intent is to move the storyboard at all.