https://bugs.kde.org/show_bug.cgi?id=428291
Tymond <tamtamy.tym...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tamtamy.tym...@gmail.com
--- Comment #9 from Tymond <tamtamy.tym...@gmail.com> ---
(I wrote this comment after c4 but haven't published; still, I think it contain
info that wasn't mentioned before, so please just ignore parts that already
were).
@azlantgc can you please check if you're not having a cursor over the canvas
while making those frames? Generally for the shortcut to work, as you noticed,
the Timeline needs to be in focus. Having cursor over the canvas means that
Krita thinks you'd like to have canvas in focus, so it switches the focus
without you needing to click on it; it's useful for stuff like Move Tool and
arrow shortcuts, for example. But it also causes issues like bug 395866 and
possibly the issue we're discussing right now. Do you think that's the reason
the Timeline gets unfocused and the shortcut stops working?
Also there are multiple operations on the Timeline:
A) Create Blank/Duplicate Frame - they create just one frame in the current
frame, even if you select multiple; so not suitable for bigger amount of frames
B) Insert multiple keyframes - it calls a dialog, so not for fast creating of
frames either, although it is suitable for big number of frames
C) Insert Keyframes Left - it should just create blank frames in the whole
selected region, put it will push down the rest of the frames further down.
@azlantgc would it help you if you'd use the C option by first selecting a
range with the number of frames you want to add, and then pressing the shortcut
for C function (You can add the shortcut in the usual location)?
If C is not suitable, because it does pushed down the rest of the timeline
(it's non-destructive, won't fill the gaps), would it be fine if you used A
instead if it worked for multiple frames (which isn't the case right now - that
would be a change to make by developers)?
And btw, "Krita Next" version that Eoin mentioned right now it not suitable for
production use, unfortunately :( It contains not only lots of improvements to
Animation (Eoin and Emmet are working only on animation right now), but also
resource rewrite, which makes it a bit unstable.
--
You are receiving this mail because:
You are watching all bug changes.
