Bug 191722 - too aggressive caching in image editor
Summary: too aggressive caching in image editor
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: ImageEditor-Canvas (show other bugs)
Version: 1.0.0
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-05 19:34 UTC by Mikolaj Machowski
Modified: 2017-08-08 15:04 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.1.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mikolaj Machowski 2009-05-05 19:34:15 UTC
Version:           0.11-svn (using Devel)
Compiler:          gcc4.3.2 
OS:                Linux
Installed from:    Compiled sources

This is  usability bug/wish:

Scenario:

1) Open Image Editor with one image.
2) Close Image Editor.
3) Open Image Editor with another image.

Problem:

When opening Image Editor second time it opens with image viewed when closing and only later new image is loaded. It may cause confusion in user if it was his/her mistake and old image was opened not new.

Solution:

Cover preloaded image with something and remove this barrier after checking that requested image is the same which was in cache?
Comment 1 Marcel Wiesweg 2009-07-12 19:16:08 UTC
If I close the image editor and open it again with a new image, I see the canvas cleared until the new image is loaded.
In constrast, if I do not close the image editor, but switch windows and select a new image from the icon view to load, indeed the old image is shown until the new one is loaded, but with a waiting cursor.
Is this the problem you are reporting?

We cannot know if the image editor window is visible or not, so the problem is the same as if the user selects a new image from the thumbnail bar in the image editor itself. So this amounts to "show more clearly that another image is being loaded". I could imagine drawing a YouTube-style progress indicator over the old image, maybe with some transparency fading.
Comment 2 Marcel Wiesweg 2009-11-29 15:37:10 UTC
We can think about this progress-bar drawing later again when the new common widget is done, if it's based on QGraphicsView or similar it will be easier to do.
Comment 3 caulier.gilles 2011-11-24 10:25:30 UTC
this entry still valid with 2.x serie ?

Gilles Caulier
Comment 4 caulier.gilles 2011-12-18 17:10:43 UTC
Mik, 

This file still valid using digiKam 2.4 ?

Gilles Caulier
Comment 5 caulier.gilles 2015-07-01 06:06:14 UTC
New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?
Comment 6 caulier.gilles 2016-07-15 13:19:35 UTC
With digiKam 5.0.0, this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier