https://bugs.kde.org/show_bug.cgi?id=372040
--- Comment #12 from RJVB <rjvber...@gmail.com> --- I've been looking for a somewhat less brute work-around, because I have had a bit too many cases where I couldn't even select a variable or function by double clicking without being taken to its declaration. That may be completely unrelated, but it may also be a result of bailing out of ongoing scans unexpectedly. - Only Qt's QCoreApplication::eventDispatcher()->processEvents() tells us if any events were actually processed, QCoreApplication::sendPostedEvents() and QCoreAPplication::processEvents() do not. Knowing this for certain would probably require installing an event filter, but how? At the level of the application (KDevelopApplication), with a generic state variable that parser can (re)set and query to know if something happened requiring them to abort ongoing operations? - Being able to bail out of ongoing operations seems like a good idea in general, but only if upstream codepaths can distinguish a bail-out return from a regular return that didn't yield results. If an API has been implemented for that I completely missed it. -- You are receiving this mail because: You are watching all bug changes.
