river-layer-shell-v1

optional layer shell support

(index)

This protocol allows the river-window-management-v1 window manager to support the wlr-layer-shell-unstable-v1 protocol.

The key words "must", "must not", "required", "shall", "shall not", "should", "should not", "recommended", "may", and "optional" in this document are to be interpreted as described in IETF RFC 2119.

river_layer_shell_v1

river layer shell global interface

Interface
Version 1

This global interface should only be advertised to the client if the river_window_manager_v1 global is also advertised. Binding this interface indicates that the window manager supports layer shell.

If the window manager does not bind this interface, the compositor should not allow clients to map layer surfaces. This can be achieved by closing layer surfaces immediately.

river_layer_shell_v1.destroy

destroy the river_layer_shell_v1 object

Destructor Request
Since Version 1

This request indicates that the client will no longer use the river_layer_shell_v1 object.

river_layer_shell_v1.get_output

get layer shell output state

Request
Since Version 1

It is a protocol error to make this request more than once for a given river_output_v1 object.

ArgumentTypeDescription
idnew_id<river_layer_shell_output_v1>

outputobject<river_output_v1>

river_layer_shell_v1.get_seat

get layer shell seat state

Request
Since Version 1

It is a protocol error to make this request more than once for a given river_seat_v1 object.

ArgumentTypeDescription
idnew_id<river_layer_shell_seat_v1>

seatobject<river_seat_v1>

river_layer_shell_v1.error

Enum
Since Version 1
EntryValueSinceDescription
object_already_created01

the layer_shell_output/seat object was already created.

river_layer_shell_output_v1

layer shell output state

Interface
Version 1

The lifetime of this object is tied to the corresponding river_output_v1. This object is made inert when the river_output_v1.removed event is sent and should be destroyed.

river_layer_shell_output_v1.destroy

destroy the object

Destructor Request
Since Version 1

This request indicates that the client will no longer use the river_layer_shell_output_v1 object and that it may be safely destroyed.

This request should be made after the river_output_v1.removed event is received to complete destruction of the output.

river_layer_shell_output_v1.set_default

Set default output for layer surfaces

Request
Since Version 1

Mark this output as the default for new layer surfaces which do not request a specific output themselves. This request overrides any previous set_default request on any river_layer_shell_output_v1 object.

If no set_default request is made or if the default output is destroyed, the default output is undefined until the next set_default request.

This request modifies window management state and may only be made as part of a manage sequence, see the river_window_manager_v1 description.

river_layer_shell_output_v1.non_exclusive_area

area left after subtracting exclusive zones

Event
Since Version 1

This event indicates the area of the output remaining after subtracting the exclusive zones of layer surfaces. Exclusive zones are a hint, the window manager is free to ignore this area hint if it wishes.

The x and y values are in the global coordinate space, not relative to the position of the output.

This event will be followed by a manage_start event after all other new state has been sent by the server.

ArgumentTypeDescription
xint

yint

widthint

heightint

river_layer_shell_seat_v1

layer shell seat state

Interface
Version 1

The lifetime of this object is tied to the corresponding river_seat_v1. This object is made inert when the river_seat_v1.removed event is sent and should be destroyed.

river_layer_shell_seat_v1.destroy

destroy the object

Destructor Request
Since Version 1

This request indicates that the client will no longer use the river_layer_shell_seat_v1 object and that it may be safely destroyed.

This request should be made after the river_seat_v1.removed event is received to complete destruction of the seat.

A layer shell surface will be given exclusive keyboard focus at the end of the manage sequence in which this event is sent. The window manager may want to update window decorations or similar to indicate that no window is focused.

Until the focus_non_exclusive or focus_none event is sent, all window manager requests to change focus are ignored.

This event will be followed by a manage_start event after all other new state has been sent by the server.

A layer shell surface will be given non-exclusive keyboard focus at the end of the manage sequence in which this event is sent. The window manager may want to update window decorations or similar to indicate that no window is focused.

The window manager continues to control focus and may choose to focus a different window/shell surface at any time. If the window manager sets focus during the same manage sequence in which this event is sent, the layer surface will not be focused.

This event will be followed by a manage_start event after all other new state has been sent by the server.

No layer shell surface will have keyboard focus at the end of the manage sequence in which this event is sent. The window manager may want to return focus to whichever window last had focus, for example.

This event will be followed by a manage_start event after all other new state has been sent by the server.

Copyright