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

------- 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.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-2]

------- 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         
caulier.gilles kdemail net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
          Component|general                     |Image Editor
      everconfirmed|0                           |1



------- Additional Comments From caulier.gilles kdemail net  2006-11-17 16:10 -------
I can confirm this cache problem with current implementation.

Marcel, cache mechanism is your (:=)). Perhaps KDE API provide a way to get an  event if file have been changed by other applications...

Gilles Caulier
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

------- 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         




------- Additional Comments From marcel.wiesweg gmx de  2006-11-17 17:39 -------
Yes, KDirWatch can watch files as well.
Is this critical for 0.9.0?
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-2]

------- 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         




------- Additional Comments From caulier.gilles kdemail net  2006-11-17 18:09 -------
Marcel, try to reproduce the problem and judge if if necessary to fix it before 0.9.0 release.

Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

------- 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         




------- Additional Comments From marcel.wiesweg gmx de  2006-11-18 16:43 -------
The solution is to create a KDirWatch in the right place which watches the files currently in the cache, and remove them from the cache when changed.

I don't think this is release critical, I would prefer to fix it post-0.9.0.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

------- 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         
marcel.wiesweg gmx de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From marcel.wiesweg gmx de  2006-12-23 17:20 -------
SVN commit 616088 by mwiesweg:

Watch files contained in LoadingCache for changes from external programs:
- set a KDirWatch on all contained files
- update after cache operations


 M  +83 -3     loadingcache.cpp  
 M  +15 -2     loadingcache.h  
 M  +1 -1      loadingcacheinterface.cpp  
 M  +1 -1      loadsavetask.cpp
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

------- 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         




------- Additional Comments From polar88bear hotmail com  2007-07-18 14:12 -------
This bug was fixed in 0.9.1 but came back again in 0.9.2. Please reopen it.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel