https://bugs.kde.org/show_bug.cgi?id=398757
--- Comment #3 from TallFurryMan <eric.dejouha...@gmail.com> --- I think we should resolve this one now that clearSequence is removed. The issue was due to targetName being executed *before* clearSequence although the property setter was requested *after* clearSequence. I will remove most of the Q_NO_REPLY because there's no guarantee on the order they will execute. Our source is not prepared for this type of async calls. If you agree, of course. -- You are receiving this mail because: You are watching all bug changes.
