river-layout: add user_command_tags event

It is not guaranteed that the next layout_demand event after a user_command
event has the same active tags (for example when there are no views visible).
As an example, a user could trigger a user_command while no views are visible,
then switch to a different tag set which has active views. The active tags of
the previous layout_demand may also be different.

Therefore it is impossible to correctly implement a layout generator which has
user commands apply only to the currently active tag set, which is solved by
this patch.

1 files changed, 1 insertions, 1 deletions

diff --git a/build.zig b/build.zig
index a0909b4..659d93d 100644
--- a/build.zig
+++ b/build.zig
@@ -111,7 +111,7 @@ pub fn build(b: *zbs.Builder) !void {
 
     scanner.generate("zriver_control_v1", 1);
     scanner.generate("zriver_status_manager_v1", 3);
-    scanner.generate("river_layout_manager_v3", 1);
+    scanner.generate("river_layout_manager_v3", 2);
 
     scanner.generate("zwlr_layer_shell_v1", 4);
     scanner.generate("zwlr_output_power_manager_v1", 1);