Bug 459806 - Timeline UX: Actions on unlocked layers are blocked when the active layer happens to be locked.
Summary: Timeline UX: Actions on unlocked layers are blocked when the active layer hap...
Status: CONFIRMED
Alias: None
Product: krita
Classification: Applications
Component: Animation (show other bugs)
Version: git master (please specify the git hash!)
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-28 21:24 UTC by Emmet O'Neill
Modified: 2023-01-04 23:15 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Emmet O'Neill 2022-09-28 21:24:01 UTC
SUMMARY
If the active layer, LAYER_A, is locked and you select a frame on a different, unlocked layer, LAYER_B, that frame will not be deleted when the delete keyframe button is pushed. The same is true for adding frames.

More info:
https://invent.kde.org/graphics/krita/-/merge_requests/1597


STEPS TO REPRODUCE
1. Create a file with 2 layers.
2. Lock LAYER_A, Unlock LAYER_B
3. Make sure that the locked layer, LAYER_A, is active, and select a frame on the unlocked layer, LAYER_B.
4. Click the `Create Blank Keyframe` button 

OBSERVED RESULT
Notice that a new frame will not be added on the unlocked LAYER_B, because the active LAYER_A is locked.

EXPECTED RESULT
We should either (a) limit keyframe addition and deletion operations to the active layer like most operations within Krita, or (b) we should make sure that operations happen as expected on unlocked layers regardless of the locking status of the active layer.