rules: rename "tag" action to "tags"
This rule action accepts and assigns a set of 32 tags represented as a 32 bit integer just like all of river's other commands handling tags. Using the singular here is potentially misleading and is also inconsistent with set-view-tags, etc. which all use the plural. Sorry about the breaking change for those who use master branch, ideally I would have caught this before merging but at least I noticed before a release. This commit also does a bit of internal refactoring/cleanup of the rules system.
This commit is contained in:
@ -42,7 +42,7 @@ pub fn init(wlr_decoration: *wlr.XdgToplevelDecorationV1) void {
|
||||
wlr_decoration.events.destroy.add(&decoration.destroy);
|
||||
wlr_decoration.events.request_mode.add(&decoration.request_mode);
|
||||
|
||||
const ssd = server.config.ssd_rules.match(xdg_toplevel.view) orelse
|
||||
const ssd = server.config.rules.ssd.match(xdg_toplevel.view) orelse
|
||||
(decoration.wlr_decoration.requested_mode != .client_side);
|
||||
|
||||
// TODO(wlroots): make sure this is properly batched in a single configure
|
||||
@ -81,7 +81,7 @@ fn handleRequestMode(
|
||||
const xdg_toplevel: *XdgToplevel = @ptrFromInt(decoration.wlr_decoration.surface.data);
|
||||
const view = xdg_toplevel.view;
|
||||
|
||||
const ssd = server.config.ssd_rules.match(xdg_toplevel.view) orelse
|
||||
const ssd = server.config.rules.ssd.match(xdg_toplevel.view) orelse
|
||||
(decoration.wlr_decoration.requested_mode != .client_side);
|
||||
|
||||
if (view.pending.ssd != ssd) {
|
||||
|
Reference in New Issue
Block a user