KDirWatch vs QFileSystemWatcher

[David Faure]

On Thursday 24 October 2013 21:54:42 Sune Vuorela wrote:
> If your KDirWatch backend is QFileSystemWatcher, one of the testcases
> fails. 
> The last QVERIFY in testMoveTo never receives the signal dirty-signal it
> is looking for.

Strange, here I'm getting a failure in removeAndReAdd (every time), but 
testMoveTo passes most of the time (finally got a failure after 10 runs or 
so)...
 
In KDE4 I also get removeAndReAdd failing everytime (with 
KDIRWATCHTEST_METHOD=QFSWatch), and couldn't get testMoveTo to fail.

> Apparantly, the watch.removeFile apparantly somehow turns off the QFSW
> to not do any further notifications for what happens in the directory
> that it also is supposed to be watching.
> 
> I haven't yet fully understood what's going on here, but if someone is
> up for it, fixing it would be nice. Among others, it is the only backend
> available on windows.
> 
> This dirty patch seems to ensure that QFSW is used on your platform:

With the changes I just pushed, a better way to change the backend for 
KDirWatch is:

KDIRWATCH_METHOD=QFSWatch ./kdirwatch_unittest

-- 
David Faure, faure at kde.org, http://www.davidfaure.fr
Working on KDE, in particular KDE Frameworks 5