KDirWatch issue

[Martin Koller]

Hi,

just wondering if I'm doing something wrong or there really is a bug in KDirWatch
(I'm on openSuse Leap 42.2, KF5 5.33.0)

From the docs I understand that when I call 

KDirWatch::stopDirScan(dir);
... create files in the dir ...
KDirWatch::restartDirScan(dir)

it should not emit the dirty signal when I run this, right ?

Well, it does.
I've attached a small test.

When I modify the code and use stopScan() ... create ... startScan()
I still receive the dirty signal with the path to the file I created.

Only way it works without signal is
removeDir(dir) ... create ... addDir(dir)

Is this how it's supposed to work ?

-- 
Best regards/Schöne Grüße

Martin
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?

()  ascii ribbon campaign - against html e-mail 
/\                        - against proprietary attachments

Geschenkideen, Accessoires, Seifen, Kulinarisches: www.lillehus.at
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CMakeLists.txt
Type: text/x-cmake
Size: 350 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20170424/34000436/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: main.cxx
Type: text/x-c++src
Size: 1008 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20170424/34000436/attachment.cxx>