Bug 413859 - Pre-cached frames don't save current frame.
Summary: Pre-cached frames don't save current frame.
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: Animation (show other bugs)
Version: nightly build (please specify the git hash!)
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-06 00:09 UTC by Ralek Kolemios
Modified: 2020-03-05 00:13 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
uncached frame (7.52 KB, image/png)
2019-11-06 00:09 UTC, Ralek Kolemios
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ralek Kolemios 2019-11-06 00:09:19 UTC
Created attachment 123742 [details]
uncached frame

SUMMARY
If the current frame is frame 2, and Krita caches frames in the background, it fails to cache the current viewed frame. When drag scrubbing through frames afterwards, the failed frame does not show up unless explicitly clicked on.

STEPS TO REPRODUCE
-Make an animation with several frames each with their own keyframe
-force a background re-cache by setting caching to on-disk or on-memory
-observe which frames were cached and which weren't
-scrubbing through the frames by dragging fails to show the uncached frame, or re-cache it


Krita
  Version: 4.3.0-prealpha (git 2c21a4c)

Qt
  Version (compiled): 5.12.5
  Version (loaded): 5.12.5

OS Information
  Build ABI: x86_64-little_endian-llp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: winnt
  Kernel Version: 10.0.17134
  Pretty Productname: Windows 10 (10.0)
Comment 1 Eoin O'Neill 2020-03-05 00:13:18 UTC
This bug has been fixed via the following merge request: 

https://invent.kde.org/kde/krita/-/merge_requests/259