[frameworks-kcoreaddons] [Bug 384866] KDirWatch::addDir should pump the eventloop (call QCoreApplication::processEvents())

https://bugs.kde.org/show_bug.cgi?id=384866 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|NOT A BUG

[frameworks-kcoreaddons] [Bug 384866] KDirWatch::addDir should pump the eventloop (call QCoreApplication::processEvents())

https://bugs.kde.org/show_bug.cgi?id=384866 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular

[frameworks-kcoreaddons] [Bug 384866] KDirWatch::addDir should pump the eventloop (call QCoreApplication::processEvents())

https://bugs.kde.org/show_bug.cgi?id=384866 --- Comment #3 from Harald Sitter --- Use KDirWatch in a thread is what I mean. Sending synchronization between a file watcher thread and the gui thread is loads less problematic then effectively doing nested ::exec() behavior inside a library. Nested

[frameworks-kcoreaddons] [Bug 384866] KDirWatch::addDir should pump the eventloop (call QCoreApplication::processEvents())

https://bugs.kde.org/show_bug.cgi?id=384866 --- Comment #2 from RJVB --- I don't think it's a good idea to handle GUI events anywhere but on the main thread - on Mac at least. Unless you meant to call KDirWatch::addDir() on its own thread? This ticket is 2 years old. It's not impossible that I

[frameworks-kcoreaddons] [Bug 384866] KDirWatch::addDir should pump the eventloop (call QCoreApplication::processEvents())

https://bugs.kde.org/show_bug.cgi?id=384866 Harald Sitter changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC|