https://bugs.kde.org/show_bug.cgi?id=379359
Bug ID: 379359
Summary: KDirWatch stopDirScan still emitting dirty signal
Product: frameworks-kcoreaddons
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: mp...@kde.org
Reporter: kol...@aon.at
CC: kdelibs-b...@kde.org
Target Milestone: ---
Created attachment 105277
--> https://bugs.kde.org/attachment.cgi?id=105277&action=edit
testprogram
(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 ?
--
You are receiving this mail because:
You are watching all bug changes.
