| Summary: | KDirWatch stopDirScan still emitting dirty signal | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kcoreaddons | Reporter: | Martin Koller <kollix> |
| Component: | general | Assignee: | Michael Pyne <mpyne> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | kdelibs-bugs |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
testprogram
cmake file to compile main.cxx |
||
Created attachment 105278 [details]
cmake file to compile main.cxx
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! still the same Operating System: openSUSE Tumbleweed 20221031 KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.5-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 Manufacturer: HP Product Name: HP ProBook 650 G2 |
Created attachment 105277 [details] 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 ?