Cancel an ensure_next_key_eaten request.

This requests cancels the effect of the latest ensure_next_key_eaten request if no key has been eaten due to the request yet. This request has no effect if a key has already been eaten or no ensure_next_key_eaten was made.

Rationale: the window manager may wish cancel an uncompleted "chorded" keybinding after a timeout of a few seconds. Note that since this timeout use-case requires the window manager to trigger a manage sequence with the river_window_manager_v1.manage_dirty request it is possible that the ate_unbound_key key event may be sent before the window manager has a chance to make the cancel_ensure_next_key_eaten 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.

Ensure the next key press event is eaten.

Ensure that the next non-modifier key press and corresponding release events for this seat are not sent to the currently focused surface.

If the next non-modifier key press triggers a binding, the pressed/released events are sent to the river_xkb_binding_v1 object as usual.

If the next non-modifier key press does not trigger a binding, the ate_unbound_key event is sent instead.

Rationale: the window manager may wish to implement "chorded" keybindings where triggering a binding activates a "submap" with a different set of keybindings. Without a way to eat the next key press event, there is no good way for the window manager to know that it should error out and exit the submap when a key not bound in the submap is pressed.

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

Destroy the object.

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

Watch for change in active modifiers.

Request that the server send the modifiers_update event whenever a state change occurs for at least one of the modifiers specified by the modifiers argument.

The window manager should make this request with the modifiers argument set to 0 when it no longer wishes to take action based on a change in modifiers.

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

Handler for a proxy with version >= 1.

Handler for a proxy with version >= 2.

Handler for a proxy with version >= 3.