[krita] [Bug 445657] Loading 250 Frames performance problem and jump back/forward buttons doesn't seem to do ANYTHING

[Emmet O'Neill]

https://bugs.kde.org/show_bug.cgi?id=445657

Emmet O'Neill <emmetoneill.pdx at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REPORTED                    |RESOLVED
         Resolution|---                         |WORKSFORME
                 CC|                            |emmetoneill.pdx at gmail.com

--- Comment #5 from Emmet O'Neill <emmetoneill.pdx at gmail.com> ---
(In reply to Hoang Duy Tran from comment #4)
> I was using nightly build (krita-nightly_d2f29d7.dmg), downloaded on
> 14/11/2021. After read your comment, I went to download the
> 'krita-5.0.0-beta2.dmg' (today, 18/11/2021) and was able loading all 250
> frames, with little delay (sustainable), I still notice the delay when I
> started playing 'Cache regeneration..' but no 99% stuck as previous version.
> Still the 'Skip Back' button moves 1 frame backward, identical to the 'Back'
> button, and 'Skip Forward' button is functioning exactly like the 'Forward'
> button. I don't understand why you'd need TWO BUTTONS performing exactly the
> same function. If I was editing I would JUMP by my mouse to a position where
> I would like to place my next frame, this must be done by MOUSE POINTER,
> only when I would like to jump to the beginning should I use 'Skip Back' (or
> rather misleading name, it looks more like 'First Frame' button) and the
> other looks more like 'Last Frame' button, honestly.

The "skip forward" button will jump to the next available keyframe on the
active layer. 
As such, if a keyframe exists on every available frame (on 1s, in animation
talk), both the next/skip forward buttons will appear to do the same thing.
As of now, if there are no keyframes on the active layer, nothing happens when
you when you hit the skip buttons.
We could probably still do something useful in that edge case, but I believe
the buttons are working as they should.

If things are not working as you expect, it's probably that you have the wrong
layer active.

Anyway, if this bug is something that can no longer be reproduced, I'm going to
close this report for now.
Thanks all.

-- 
You are receiving this mail because:
You are watching all bug changes.