https://bugs.kde.org/show_bug.cgi?id=503813
--- Comment #38 from Igor Kushnir <igor...@gmail.com> --- Created attachment 181127 --> https://bugs.kde.org/attachment.cgi?id=181127&action=edit Second context menu: call stack with debug symbols Analyzed the second context menu call stack with debug symbols (attached) in KDevelop after following the instructions in my comments #5 and #6 to Bug 486932. Qt gets to QCoreApplication::notifyInternal2() and eventually to KateViewInternal::contextMenuEvent() with different preceding call stacks in the primary and the nested event loop. Maybe the same context menu event is delivered again before being accepted? If the event duplication is reproducible with a small Qt-only example (just override QWidget::contextMenuEvent() and process events before accepting the event), it can be reported as a Qt bug. Maybe KateViewInternal::contextMenuEvent() can detect that the event is spurious or something (or perhaps the second event is exactly the same as the event that is currently being handled) and return early instead of handling it (not sure whether to accept or reject the extra event). Changing the relevant context menu handling logic in KDevelop code seems difficult and risky because of the extreme complexity of the current context menu workflow as the commit message of https://commits.kde.org/kdevelop/d940a88e8bd92031cd7ffce2450cc24f266e6acc explains. -- You are receiving this mail because: You are watching all bug changes.
