[Okular-devel] [okular] [Bug 316890] Intelligent automatic reload

Vishesh Handa me at vhanda.in
Mon Apr 15 07:45:12 UTC 2013


https://bugs.kde.org/show_bug.cgi?id=316890

Vishesh Handa <me at vhanda.in> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |me at vhanda.in

--- Comment #11 from Vishesh Handa <me at vhanda.in> ---
inotify has a 2 modification events - 

IN_MODIFY - Emitted anytime a file is modified
IN_CLOSE_WRITE - when a file that is opened with a write flag is closed
regardless of the modifications. 

For Nepomuk we only use the IN_CLOSE_WRITE signal and then manually check if
the mtime of the file has changed. Many programs open files under write mode
even when no modifications are to be made -eg Taglib. Some programs, such as
KTorrent, are even worse and keep opening and closing files with write flags
when seeding.

I had a look at KDirWatch and it only checks for the IN_MODIFY signal. I'm not
sure how one would go along implementing IN_CLOSE_WRITE. Nepomuk uses inotify
directly cause of our special requirements instead of going through KDirWatch.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Okular-devel mailing list