sway-patched-tray-menu-github/include/sway/xdg_decoration.h

#ifndef _SWAY_XDG_DECORATION_H
#define _SWAY_XDG_DECORATION_H

#include <wlr/types/wlr_xdg_decoration_v1.h>

struct sway_xdg_decoration {
	struct wlr_xdg_toplevel_decoration_v1 *wlr_xdg_decoration;
	struct wl_list link;

	struct sway_view *view;

	struct wl_listener destroy;
	struct wl_listener request_mode;
};

struct sway_xdg_decoration *xdg_decoration_from_surface(
	struct wlr_surface *surface);

void set_xdg_decoration_mode(struct sway_xdg_decoration *deco);

#endif
Add CSD to border modes This replaces view.using_csd with a new border mode: B_CSD. This also removes sway_xdg_shell{_v6}_view.deco_mode and view->has_client_side_decorations as we can now get these from the border. You can use `border toggle` to cycle through the modes including CSD, or use `border csd` to set it directly. The client must support the xdg-decoration protocol, and the only client I know of that does is the example in wlroots. If the client switches from SSD to CSD without us expecting it (via the server-decoration protocol), we stash the previous border type into view.saved_border so we can restore it if the client returns to SSD. I haven't found a way to test this though. 2018-09-24 12:54:57 +02:00			`#ifndef _SWAY_XDG_DECORATION_H`
			`#define _SWAY_XDG_DECORATION_H`

			`#include <wlr/types/wlr_xdg_decoration_v1.h>`

			`struct sway_xdg_decoration {`
			`struct wlr_xdg_toplevel_decoration_v1 *wlr_xdg_decoration;`
			`struct wl_list link;`

			`struct sway_view *view;`

			`struct wl_listener destroy;`
Improve CSD logic This does the following: * Removes the xdg-decoration surface_commit listener. I was under the impression the client could ignore the server's preference and set whatever decoration they like using this protocol, but I don't think that's right. * Adds a listener for the xdg-decoration request_mode signal. The protocol states that the server should respond to this with its preference. We'll always respond with SSD here. * Makes it so tiled views which use CSD will still have sway decorations rendered. To do this, using_csd had to be added back to the view struct, and the border is changed when floating or unfloating a view. 2018-09-27 14:44:57 +02:00			`struct wl_listener request_mode;`
Add CSD to border modes This replaces view.using_csd with a new border mode: B_CSD. This also removes sway_xdg_shell{_v6}_view.deco_mode and view->has_client_side_decorations as we can now get these from the border. You can use `border toggle` to cycle through the modes including CSD, or use `border csd` to set it directly. The client must support the xdg-decoration protocol, and the only client I know of that does is the example in wlroots. If the client switches from SSD to CSD without us expecting it (via the server-decoration protocol), we stash the previous border type into view.saved_border so we can restore it if the client returns to SSD. I haven't found a way to test this though. 2018-09-24 12:54:57 +02:00			`};`

			`struct sway_xdg_decoration *xdg_decoration_from_surface(`
			`struct wlr_surface *surface);`

xdg-shell: chase events update 2023-07-11 14:09:14 +02:00			`void set_xdg_decoration_mode(struct sway_xdg_decoration *deco);`

Add CSD to border modes This replaces view.using_csd with a new border mode: B_CSD. This also removes sway_xdg_shell{_v6}_view.deco_mode and view->has_client_side_decorations as we can now get these from the border. You can use `border toggle` to cycle through the modes including CSD, or use `border csd` to set it directly. The client must support the xdg-decoration protocol, and the only client I know of that does is the example in wlroots. If the client switches from SSD to CSD without us expecting it (via the server-decoration protocol), we stash the previous border type into view.saved_border so we can restore it if the client returns to SSD. I haven't found a way to test this though. 2018-09-24 12:54:57 +02:00			`#endif`