[direct edit] moving to next/previous image is slow
Submitted by Adam Dingle
Link to original bug (#718316)
Description
---- Reported by adam@yorba.org 2012-03-26 20:36:00 -0700 ----
Original Redmine bug id: 4937
Original URL: http://redmine.yorba.org/issues/4937
Searchable id: yorba-bug-4937
Original author: Adam Dingle
Original description:
To see the problem, find a folder that has several images, open one of them in direct edit mode and use the left/arrows to browse through images. Each time you press an arrow key, there is a noticeable delay before the next image appears. This is a regression from 0.11, in which the next image appeared quickly (though it was initially blurry and followed by a crisp image only after a moment).
We should read ahead so that moving between images in direct edit mode is as fast as in a Shotwell library.
Related issues:
- related to shotwell - 5202: Be smarter about pre-caching images or don't cache altoge... (Open)
---- Additional Comments From shotwell-maint@gnome.bugs 2012-09-13 15:48:00 -0700 ----
History
Comment 1
Updated by Clinton Rogers over 1 year ago
- Assignee set to Clinton Rogers
- Target version set to 0.12.1
I believe this may be due to some naive assumptions I made when I wrote the caching mechanism...
Comment 2
Updated by Clinton Rogers over 1 year ago
- Target version changed from 0.12.1 to 0.13
Comment 3
Updated by Adam Dingle over 1 year ago
-
Assignee deleted (
<strike>
_Clinton Rogers_</strike>
)
Comment 4
Updated by Adam Dingle about 1 year ago
-
Target version deleted (
<strike>
_0.13_</strike>
)
--- Bug imported by chaz@yorba.org 2013-11-25 21:56 UTC ---
This bug was previously known as bug 4937 at http://redmine.yorba.org/show_bug.cgi?id=4937
Unknown Component Using default product and component set in Parameters Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one. Resolution set on an open status. Dropping resolution
Resolution: RESOLVED FIXED