You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reading https://blog.broulik.de/2016/10/global-menus-returning/ it seems we'd need to use the (Qt proprietary?) Extended Surface Wayland protocol which allows you to set (and read?) arbitrary properties on a window. We'd likely need to use this (instead of X11 atoms) to get the values of the (KDE proprietary) _KDE_NET_WM_APPMENU_OBJECT_PATH and _KDE_NET_WM_APPMENU_SERVICE_NAME.
Quite we'd also need to change QtPlugin to use the (Qt proprietary?) Extended Surface Wayland protocol.
But there isn't a Wayland documentation that precisely tells you what you need to do to get global menus working.
While it's nice that KDE has found some way to make global menus work for them under Wayland, it seems very hackish and proprietary, meaning it won't work for everyone in all desktop environments.
Raspberry Pi OS, when running in Wayland (as it is the default), breaks the global menu functionality.
When I start
featherpad
, I do seecom.canonical.dbusmenu
activity.But the application menus are not shown in Menu.
Someone knowledgable in Wayland would need to look at this.
Some possibly relevant details:
The text was updated successfully, but these errors were encountered: