https://bugs.kde.org/show_bug.cgi?id=369276
--- Comment #4 from RJVB <rjvber...@gmail.com> ---
I guess this depends on exactly what you use it for in the toolbar, but yes,
it's possible.
The problem is a bit that I'm not perfectly sure exactly which classes are
concerned. The last time I've seen a real problem arise was with Kate's (and
thus KDevelop's) Mode and Highlighting menus. IIRC those are populated with
QAction instances; the symptom was that most items were disabled and some never
appeared. That corresponds to what is written in the docs for *QWidgetAction* :
OS X: If you add a widget to a menu in the application's menu bar on OS X,
the widget will be added and it will function but with some limitations:
1. The widget is reparented away from the QMenu to the native menu view. If
you show the menu in some other place (e.g. as a popup menu), the widget will
not be there.
What makes this extra annoying is that it is hard to predict exactly what
happens. The claim above ("will not be there") is not necessarily true for
instance, at least not always. Usually I've been able to see the items in both
the native menu and a context menu, for instance. And the Mode/Highlighting
issue in Kate weren't affected from my first attempts with KF5 (Kate was the
1st app I built). They worked, but the Bookmark menu didn't; the Mode and
Highlighting menus were affected only recently but the code didn't or hardly
change. IOW, the actual effects of the reparenting *may* depend on the order in
which things happen, which could depend on changes in related code (kxmlgui..)
or even compiler options (I think).
I'll try to find some time tomorrow to see exactly what was being added to
those Kate menus that remained disabled (but I take it that the limitation
would be almost just as unacceptable for QWidgetActions?).
--
You are receiving this mail because:
You are watching all bug changes.
