xdg_output_unstable_v1 Module

ZxdgOutputManagerV1

class pywayland.protocol.xdg_output_unstable_v1.ZxdgOutputManagerV1

Manage xdg_output objects

A global factory interface for xdg_output objects.

destroy()

Request – opcode 0 (attached to Resource instance)

Destroy the xdg_output_manager object

Using this request a client can tell the server that it is not going to use the xdg_output_manager object anymore.

Any objects already created through this instance are not affected.

get_xdg_output(output)

Request – opcode 1 (attached to Resource instance)

Create an xdg output from a WlOutput

This creates a new xdg_output object for the given WlOutput.

Parameters:output (WlOutput) –
Returns:ZxdgOutputV1

ZxdgOutputV1

class pywayland.protocol.xdg_output_unstable_v1.ZxdgOutputV1

Compositor logical output region

An xdg_output describes part of the compositor geometry.

This typically corresponds to a monitor that displays part of the compositor space.

For objects version 3 onwards, after all xdg_output properties have been sent (when the object is created and when properties are updated), a WlOutput.done() event is sent. This allows changes to the output properties to be seen as atomic, even if they happen via multiple events.

destroy()

Request – opcode 0 (attached to Resource instance)

Destroy the xdg_output object

Using this request a client can tell the server that it is not going to use the xdg_output object anymore.

logical_position(x, y)

Event – opcode 0 (attached to Proxy instance)

Position of the output within the global compositor space

The position event describes the location of the WlOutput within the global compositor space.

The logical_position event is sent after creating an xdg_output (see xdg_output_manager.get_xdg_output) and whenever the location of the output changes within the global compositor space.

Parameters:
  • x (int) – x position within the global compositor space
  • y (int) – y position within the global compositor space
logical_size(width, height)

Event – opcode 1 (attached to Proxy instance)

Size of the output in the global compositor space

The logical_size event describes the size of the output in the global compositor space.

For example, a surface without any buffer scale, transformation nor rotation set, with the size matching the logical_size will have the same size as the corresponding output when displayed.

Most regular Wayland clients should not pay attention to the logical size and would rather rely on XdgShell interfaces.

Some clients such as Xwayland, however, need this to configure their surfaces in the global compositor space as the compositor may apply a different scale from what is advertised by the output scaling property (to achieve fractional scaling, for example).

For example, for a WlOutput mode 3840×2160 and a scale factor 2:

  • A compositor not scaling the surface buffers will advertise a logical size of 3840×2160,
  • A compositor automatically scaling the surface buffers will advertise a logical size of 1920×1080,
  • A compositor using a fractional scale of 1.5 will advertise a logical size to 2560×1620.

For example, for a WlOutput mode 1920×1080 and a 90 degree rotation, the compositor will advertise a logical size of 1080x1920.

The logical_size event is sent after creating an xdg_output (see xdg_output_manager.get_xdg_output) and whenever the logical size of the output changes, either as a result of a change in the applied scale or because of a change in the corresponding output mode(see WlOutput.mode()) or transform (see WlOutput.transform()).

Parameters:
  • width (int) – width in global compositor space
  • height (int) – height in global compositor space
done()

Event – opcode 2 (attached to Proxy instance)

All information about the output have been sent

This event is sent after all other properties of an xdg_output have been sent.

This allows changes to the xdg_output properties to be seen as atomic, even if they happen via multiple events.

For objects version 3 onwards, this event is deprecated. Compositors are not required to send it anymore and must send WlOutput.done() instead.

name(name)

Event – opcode 3 (attached to Proxy instance)

Name of this output

Many compositors will assign names to their outputs, show them to the user, allow them to be configured by name, etc. The client may wish to know this name as well to offer the user similar behaviors.

The naming convention is compositor defined, but limited to alphanumeric characters and dashes (-). Each name is unique among all WlOutput globals, but if a WlOutput global is destroyed the same name may be reused later. The names will also remain consistent across sessions with the same hardware and software configuration.

Examples of names include ‘HDMI-A-1’, ‘WL-1’, ‘X11-1’, etc. However, do not assume that the name is a reflection of an underlying DRM connector, X11 connection, etc.

The name event is sent after creating an xdg_output (see xdg_output_manager.get_xdg_output). This event is only sent once per xdg_output, and the name does not change over the lifetime of the WlOutput global.

Parameters:name (string) – output name
description(description)

Event – opcode 4 (attached to Proxy instance)

Human-readable description of this output

Many compositors can produce human-readable descriptions of their outputs. The client may wish to know this description as well, to communicate the user for various purposes.

The description is a UTF-8 string with no convention defined for its contents. Examples might include ‘Foocorp 11” Display’ or ‘Virtual X11 output via :1’.

The description event is sent after creating an xdg_output (see xdg_output_manager.get_xdg_output) and whenever the description changes. The description is optional, and may not be sent at all.

For objects of version 2 and lower, this event is only sent once per xdg_output, and the description does not change over the lifetime of the WlOutput global.

Parameters:description (string) – output description