https://bugs.kde.org/show_bug.cgi?id=475550
--- Comment #7 from rebuilders...@gmail.com ---
Thank you for the fix. This is safer now, but it's still not perfect. For one
thing, if you create a layer to paint on, then scrub around the timeline, the
contents of that layer are displayed on other
https://bugs.kde.org/show_bug.cgi?id=475550
Dmitry Kazakov changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap
https://bugs.kde.org/show_bug.cgi?id=475550
Dmitry Kazakov changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=475550
--- Comment #4 from rebuilders...@gmail.com ---
(In reply to Dmitry Kazakov from comment #2)
> How about the following solution:
>
> 1) When merging a non-animated layer over the top of an animated one, the
> layer is merged into the **current frame**
https://bugs.kde.org/show_bug.cgi?id=475550
--- Comment #3 from Bug Janitor Service ---
A possibly relevant merge request was started @
https://invent.kde.org/graphics/krita/-/merge_requests/1962
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475550
--- Comment #2 from Dmitry Kazakov ---
How about the following solution:
1) When merging a non-animated layer over the top of an animated one, the layer
is merged into the **current frame** (potentially, with auto-keyframing)
2) The user will also
https://bugs.kde.org/show_bug.cgi?id=475550
wolthera changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
