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§
- ExtWorkspace
Manager V1 - list and control workspaces
Enums§
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