This protocol allows clients to get updates from dwl and vice versa. Warning! This protocol is experimental and may make backward incompatible changes. This interface is exposed as a global in wl_registry. Clients can use this interface to get a dwl_output. After binding the client will revieve dwl_manager.tag and dwl_manager.layout events. The dwl_manager.tag and dwl_manager.layout events expose tags and layouts to the client. Indicates that the client will not the dwl_manager object anymore. Objects created through this instance are not affected. Get a dwl_output for the specified wl_output. This event is sent after binding. A roundtrip after binding guarantees the client recieved all tags. This event is sent after binding. A roundtrip after binding guarantees the client recieved all layouts. Observe and control a dwl output. Events are double-buffered: Clients should cache events and redraw when a dwl_output.done event is sent. Request are not double-buffered: The compositor will update immediately upon request. Indicates to that the client no longer needs this dwl_output. Indicates the client should hide or show themselves. If the client is visible then hide, if hidden then show. Indicates if the output is active. Zero is invalid, nonzero is valid. Indicates that a tag has been updated. Indicates a new layout is selected. Indicates the title has changed. Indicates that a sequence of status updates have finished and the client should redraw. The tags are updated as follows: new_tags = (current_tags AND and_tags) XOR xor_tags