GNOME Bugzilla – Bug 710056
wayland: Support always-on-top / sticky windows
Last modified: 2013-10-29 21:12:42 UTC
Use the new gtk-shell APIs available in mutter to add support for this.
Created attachment 257190 [details] [review] wayland: Support always-on-top / sticky windows
looks like this is missing a way to get the current workspace, as well as the number of workspaces. Look at the x11 api for inspiration. This information is needed to implement some of the window menu functionality.
Review of attachment 257190 [details] [review]: looks good apart from the previous comment
*** Bug 707079 has been marked as a duplicate of this bug. ***
(In reply to comment #2) > looks like this is missing a way to get the current workspace, as well as the > number of workspaces. Look at the x11 api for inspiration. This information is > needed to implement some of the window menu functionality. It looks like <event name="workspace_changed"> will communicate the current workspace, and I think it should be sent to any client who gets the gtk surface extension object, as well as when the current workspace changes. This way there will be no need for roundtrips. I think number of workspaces should be communicated in a similar way. In my workspace extension in weston I simply had a state event that communicated both active workspace and number of workspaces.
Attachment 257190 [details] pushed as b3cffb8 - wayland: Support always-on-top / sticky windows