Summary: | adding menu as submenu (too?) leads to repeated "InsertNative: item is already in menu" errors | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-ktexteditor | Reporter: | RJVB <rjvbertin> |
Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | jpwhiting |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | macOS | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
RJVB
2015-12-13 09:21:48 UTC
As an additional observation: Running kate5 on OS X using the XCB plugin is possible even without all X11-specific code included. It may not make much sense, but it does add an interesting observation: the application doesn't get a menubar. Regular/simple Qt applications will get a window-based menubar instead of the Mac-style menubar when run with the XCB QPA; if that doesn't happen that often means that Qt::AA_DontUseNativeMenuBar is set explicitly (normally the platform plugin does that). I cannot find a trace of setting AA_DontUseNativeMenuBar in any of the KF5 frameworks (or Kate' s code itself), but when I set that attribute in Kate's kdemain function something else happens. The application gets TWO menubars. And that leads to many more of the above error messages, concerning other items. I think that lends a lot of support to my hypothesis re: adding QWidgetAction to multiple menus. Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. |