aboutsummaryrefslogtreecommitdiff
path: root/rivertile
diff options
context:
space:
mode:
authorLeon Henrik Plickat <leonhenrik.plickat@stud.uni-goettingen.de>2022-08-14 16:34:18 +0200
committerIsaac Freund <mail@isaacfreund.com>2022-08-16 13:40:07 +0200
commit844ffce03738d003a149ad9f022005f897194b2e (patch)
tree53bf5fd5307d59eae7143b4c7f8e1c4962bc4d20 /rivertile
parent416fdc8d06c64e8c4a52dd5558e641c396ebf3cd (diff)
downloadriver-844ffce03738d003a149ad9f022005f897194b2e.tar.gz
river-844ffce03738d003a149ad9f022005f897194b2e.tar.xz
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.
Diffstat (limited to 'rivertile')
-rw-r--r--rivertile/main.zig1
1 files changed, 1 insertions, 0 deletions
diff --git a/rivertile/main.zig b/rivertile/main.zig
index 0e9276b..bf28bf7 100644
--- a/rivertile/main.zig
+++ b/rivertile/main.zig
@@ -298,6 +298,7 @@ const Output = struct {
.bottom => layout.commit("rivertile - bottom", ev.serial),
}
},
+ .user_command_tags => {},
}
}
};