Module ext_workspace_manager_v1

Source
Expand description

list and control workspaces

Workspaces, also called virtual desktops, are groups of surfaces. A compositor with a concept of workspaces may only show some such groups of surfaces (those of ‘active’ workspaces) at a time. ‘Activating’ a workspace is a request for the compositor to display that workspace’s surfaces as normal, whereas the compositor may hide or otherwise de-emphasise surfaces that are associated only with ‘inactive’ workspaces. Workspaces are grouped by which sets of outputs they correspond to, and may contain surfaces only from those outputs. In this way, it is possible for each output to have its own set of workspaces, or for all outputs (or any other arbitrary grouping) to share workspaces. Compositors may optionally conceptually arrange each group of workspaces in an N-dimensional grid.

The purpose of this protocol is to enable the creation of taskbars and docks by providing them with a list of workspaces and their properties, and allowing them to activate and deactivate workspaces.

After a client binds the ext_workspace_manager_v1, each workspace will be sent via the workspace event.

Structs§

ExtWorkspaceManagerV1
list and control workspaces

Enums§

Event
Request

Constants§

EVT_DONE_OPCODE
The wire opcode for this event
EVT_DONE_SINCE
The minimal object version supporting this event
EVT_FINISHED_OPCODE
The wire opcode for this event
EVT_FINISHED_SINCE
The minimal object version supporting this event
EVT_WORKSPACE_GROUP_OPCODE
The wire opcode for this event
EVT_WORKSPACE_GROUP_SINCE
The minimal object version supporting this event
EVT_WORKSPACE_OPCODE
The wire opcode for this event
EVT_WORKSPACE_SINCE
The minimal object version supporting this event
REQ_COMMIT_OPCODE
The wire opcode for this request
REQ_COMMIT_SINCE
The minimal object version supporting this request
REQ_STOP_OPCODE
The wire opcode for this request
REQ_STOP_SINCE
The minimal object version supporting this request