https://bugs.kde.org/show_bug.cgi?id=400034
--- Comment #1 from Chris Holland <[email protected]> --- Last I looked into using the GlobalMenu (aka appmenu) widget's code, it wouldn't work since you'd need the plugin namespace to be org.kde.appmenu. You need the appmenu's nativeInterface to even trigger a button. * https://github.com/KDE/plasma-workspace/blob/master/applets/appmenu/package/metadata.desktop#L84 * https://github.com/KDE/plasma-workspace/blob/master/applets/appmenu/package/contents/ui/main.qml#L39 * https://github.com/KDE/plasma-workspace/blob/master/applets/appmenu/package/contents/ui/main.qml#L133 This is why AWC was forced to copy the appmenu code. As for "embedding" the widget... Hmmm. It's possible to do (like the System Tray or the Group widget), but I've never done that before. AWC could break into 2 widgets, the "app title + window buttons" could be 1 widget, and the global menu a different widget. Global menu would need to be patched to offer the following though: * Ability to fill up the panel width * Double click to toggle maximize and all the other mouse shortcuts. An issue with making it multiple widgets is that you'd get padding between the widgets you'd have no way of controlling. So you wouldn't be able to get this exact look: https://i.imgur.com/p6UMZE2.png -- You are receiving this mail because: You are watching all bug changes.
