[Digikam-devel] [Bug 158565] Digikam 9.3 and above ignores files created through external applications like gimp

[Gilles Caulier]

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




------- Additional Comments From caulier.gilles gmail com  2008-02-29 11:19 -------
Marcus,

Sound like notification method from KDirWatch can be only changed at compilation.

Look in code :

http://websvn.kde.org/branches/KDE/3.5/kdelibs/kio/kio/kdirwatch.h?revision=484448&view=markup
http://websvn.kde.org/branches/KDE/3.5/kdelibs/kio/kio/kdirwatch.cpp?revision=556220&view=markup

...and read the comment. It's very intructive...

In fact, this depand of the kernel type/version used on your system.

Marcel, are you seen this comment on the code about signals emit by KDirWatch :

// ----------------------------------------------

signals:

   /**
    * Emitted when a watched object is changed.
    * For a directory this signal is emitted when files
    * therein are created or deleted.
    * For a file this signal is emitted when its size or attributes change.
    *
    * When you watch a directory, changes in the size or attributes of
    * contained files may or may not trigger this signal to be emitted
    * depending on which backend is used by KDirWatch.
    *
    * The new ctime is set before the signal is emitted.
    *  param path the path of the file or directory
    */
   void dirty (const QString &path);

   /**
    * Emitted when a file or directory is created.
    *  param path the path of the file or directory
    */
   void created (const QString &path );
     
   /**
    * Emitted when a file or directory is deleted.
    *
    * The object is still watched for new creation.
    *  param path the path of the file or directory
    */
   void deleted (const QString &path );

// ----------------------------------------------

==> "When you watch a directory, changes in the size or attributes of
    contained files may or may not trigger this signal to be emitted
    depending on which backend is used by KDirWatch."

In AlbumManager class, we only using "dirty", not "deleted" and "created"

This can be the source of problem ???

Gilles