[Digikam-devel] [Bug 137491] New: Editor image cache not flush when an image is modified outside digikam

[polarbear]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=137491         
           Summary: Editor image cache not flush when an image is modified
                    outside digikam
           Product: digikam
           Version: 0.9.0-beta3
          Platform: Gentoo Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: digikam-devel kde org
        ReportedBy: polar88bear hotmail com


Version:           0.9.0-beta3 (using KDE KDE 3.5.5)
Installed from:    Gentoo Packages
Compiler:          gcc-4.1 
OS:                Linux

Starting from Digikam-0.9.0-beta1, the most recently viewed images are cached (perhaps pre-fetched). However, when an image is modified outside digikam, e.g. in gimp, while digikam is running, digikam is not intelligent enough to notice the change in the image and flush the cache. In another words, if I open an image with an external editor from digikam, have the image edited and saved, when I return to digikam and view the image, I still see the unedited version of the image. The only way to see the view the new version of the image is to restart digikam. Which effective flushes all in-memory cache.