From 2da4e1e93846c6115ad111aae6b345067cc691a9 Mon Sep 17 00:00:00 2001 From: Squibid Date: Fri, 12 Dec 2025 15:41:42 -0500 Subject: [PATCH] update wlr-layer-shell-unstable-v1 to 5 and increment other protcol numbers --- build.zig | 10 +++++----- protocols/wlr-layer-shell-unstable-v1.xml | 21 +++++++++++++++++++-- 2 files changed, 24 insertions(+), 7 deletions(-) diff --git a/build.zig b/build.zig index 2969ec3..3b7542a 100644 --- a/build.zig +++ b/build.zig @@ -32,14 +32,14 @@ pub fn build(b: *std.Build) void { scanner.generate("zmez_remote_lua_manager_v1", 1); scanner.generate("wl_compositor", 6); scanner.generate("wl_subcompositor", 1); - scanner.generate("wl_shm", 1); + scanner.generate("wl_shm", 2); scanner.generate("wl_output", 4); - scanner.generate("wl_seat", 7); + scanner.generate("wl_seat", 9); scanner.generate("wl_data_device_manager", 3); scanner.generate("zxdg_decoration_manager_v1", 1); - scanner.generate("xdg_wm_base", 6); - scanner.generate("zwp_tablet_manager_v2", 1); - scanner.generate("zwlr_layer_shell_v1", 4); + scanner.generate("xdg_wm_base", 7); + scanner.generate("zwp_tablet_manager_v2", 2); + scanner.generate("zwlr_layer_shell_v1", 5); const wayland = b.createModule(.{ .root_source_file = scanner.result }); const xkbcommon = b.dependency("xkbcommon", .{}).module("xkbcommon"); diff --git a/protocols/wlr-layer-shell-unstable-v1.xml b/protocols/wlr-layer-shell-unstable-v1.xml index d62fd51..e9f27e4 100644 --- a/protocols/wlr-layer-shell-unstable-v1.xml +++ b/protocols/wlr-layer-shell-unstable-v1.xml @@ -25,7 +25,7 @@ THIS SOFTWARE. - + Clients can use this interface to assign the surface_layer role to wl_surfaces. Such surfaces are assigned to a "layer" of the output and @@ -100,7 +100,7 @@ - + An interface that may be implemented by a wl_surface, for surfaces that are designed to be rendered as a layer of a stacked desktop-like @@ -367,6 +367,7 @@ + @@ -386,5 +387,21 @@ + + + + + + Requests an edge for the exclusive zone to apply. The exclusive + edge will be automatically deduced from anchor points when possible, + but when the surface is anchored to a corner, it will be necessary + to set it explicitly to disambiguate, as it is not possible to deduce + which one of the two corner edges should be used. + + The edge must be one the surface is anchored to, otherwise the + invalid_exclusive_edge protocol error will be raised. + + +