| Summary: | Duplicating / Pasting Animated Layer doesn't move the frame selection properly. | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | Emmet O'Neill <emmetoneill.pdx> |
| Component: | Animation | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | minor | CC: | dimula73 |
| Priority: | NOR | ||
| Version First Reported In: | git master (please specify the git hash!) | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Emmet O'Neill
2024-09-06 23:14:51 UTC
Hi, Emmet! I cannot reproduce the issue here locally (at least on Windows). I have two different ways how it behaves and it looks consistent with the rest of list-box behavior: Case 1: frame selection is on the currently active layer, and active layer is duplicated 1) Select a layer, select a frame on this layer on the timeline 2) Duplicate this very layer 3) The new layer appears on the timeline and a frame is selected on it (as expected) Case 2: frame selection is on any non-active layer, and active layer is duplicated 1) Select a layer, select a frame on any different layer 2) Duplicate active layer 3) The new layer appears on the timeline, but the frame is still selected on the old layer (since it is not on the active layer) Can you confirm that the both cases work as I describe that? Or it works differently on Linux? This behavior is the standard behavior of Qt's list controls. I'm not really sure we should change that (though we could discuss that with a wider community). Add needsinfo Hey Dmitry, I think you're right because I can't reproduce this anymore either, which either means I was confused somehow (most likely... probably...) or there is some rare condition involved. The other day when I was testing for a different bug I felt like I ran into some unexpected behavior, but everything seems to be working as expected now. *shrug* Let's go ahead and close this for now, and I'll open it again in the future if I happen to run into something unexpected again. Sorry for the false alarm. lol :) |