xdg_shell Module¶

XdgToplevel¶

class pywayland.protocol.xdg_shell.XdgToplevel¶

Toplevel surface

This interface defines an XdgSurface role which allows a surface to, among other things, set window-like properties such as maximize, fullscreen, and minimize, set application- specific metadata like title and id, and well as trigger user interactive operations such as interactive resize and move.

Unmapping an XdgToplevel means that the surface cannot be shown by the compositor until it is explicitly mapped again. All active operations (e.g., move, resize) are canceled and all attributes (e.g. title, state, stacking, …) are discarded for an XdgToplevel surface when it is unmapped.

Attaching a null buffer to a toplevel unmaps the surface.

destroy()¶

Request – opcode 0 (attached to Resource instance)

Destroy the XdgToplevel

This request destroys the role surface and unmaps the surface; see “Unmapping” behavior in interface section for details.

set_parent(parent)¶

Request – opcode 1 (attached to Resource instance)

Set the parent of this surface

Set the “parent” of this surface. This surface should be stacked above the parent surface and all other ancestor surfaces.

Parent windows should be set on dialogs, toolboxes, or other “auxiliary” surfaces, so that the parent is raised when the dialog is raised.

Setting a null parent for a child window removes any parent-child relationship for the child. Setting a null parent for a window which currently has no parent is a no-op.

If the parent is unmapped then its children are managed as though the parent of the now-unmapped parent has become the parent of this surface. If no parent exists for the now-unmapped parent then the children are managed as though they have no parent surface.

Parameters:	parent (`XdgToplevel` or None) –

set_title(title)¶

Request – opcode 2 (attached to Resource instance)

Set surface title

Set a short title for the surface.

This string may be used to identify the surface in a task bar, window list, or other user interface elements provided by the compositor.

The string must be encoded in UTF-8.

Parameters:	title (string) –

set_app_id(app_id)¶

Request – opcode 3 (attached to Resource instance)

Set application id

Set an application identifier for the surface.

The app ID identifies the general class of applications to which the surface belongs. The compositor can use this to group multiple surfaces together, or to determine how to launch a new application.

For D-Bus activatable applications, the app ID is used as the D-Bus service name.

The compositor shell will try to group application surfaces together by their app ID. As a best practice, it is suggested to select app ID’s that match the basename of the application’s .desktop file. For example, “org.freedesktop.FooViewer” where the .desktop file is “org.freedesktop.FooViewer.desktop”.

Like other properties, a set_app_id request can be sent after the XdgToplevel has been mapped to update the property.

See the desktop-entry specification [0] for more details on application identifiers and how they relate to well-known D-Bus names and .desktop files.

[0] http://standards.freedesktop.org/desktop-entry-spec/

Parameters:	app_id (string) –

show_window_menu(seat, serial, x, y)¶

Request – opcode 4 (attached to Resource instance)

Show the window menu

Clients implementing client-side decorations might want to show a context menu when right-clicking on the decorations, giving the user a menu that they can use to maximize or minimize the window.

This request asks the compositor to pop up such a window menu at the given position, relative to the local surface coordinates of the parent surface. There are no guarantees as to what menu items the window menu contains.

This request must be used in response to some sort of user action like a button press, key press, or touch down event.

Parameters:	seat (`WlSeat`) – the `WlSeat` of the user event serial (uint) – the serial of the user event x (int) – the x position to pop up the window menu at y (int) – the y position to pop up the window menu at

move(seat, serial)¶

Request – opcode 5 (attached to Resource instance)

Start an interactive move

Start an interactive, user-driven move of the surface.

This request must be used in response to some sort of user action like a button press, key press, or touch down event. The passed serial is used to determine the type of interactive move (touch, pointer, etc).

The server may ignore move requests depending on the state of the surface (e.g. fullscreen or maximized), or if the passed serial is no longer valid.

If triggered, the surface will lose the focus of the device (WlPointer, WlTouch, etc) used for the move. It is up to the compositor to visually indicate that the move is taking place, such as updating a pointer cursor, during the move. There is no guarantee that the device focus will return when the move is completed.

Parameters:	seat (`WlSeat`) – the `WlSeat` of the user event serial (uint) – the serial of the user event

resize(seat, serial, edges)¶

Request – opcode 6 (attached to Resource instance)

Start an interactive resize

Start a user-driven, interactive resize of the surface.

This request must be used in response to some sort of user action like a button press, key press, or touch down event. The passed serial is used to determine the type of interactive resize (touch, pointer, etc).

The server may ignore resize requests depending on the state of the surface (e.g. fullscreen or maximized).

If triggered, the client will receive configure events with the “resize” state enum value and the expected sizes. See the “resize” enum value for more details about what is required. The client must also acknowledge configure events using “ack_configure”. After the resize is completed, the client will receive another “configure” event without the resize state.

If triggered, the surface also will lose the focus of the device (WlPointer, WlTouch, etc) used for the resize. It is up to the compositor to visually indicate that the resize is taking place, such as updating a pointer cursor, during the resize. There is no guarantee that the device focus will return when the resize is completed.

The edges parameter specifies how the surface should be resized, and is one of the values of the resize_edge enum. The compositor may use this information to update the surface position for example when dragging the top left corner. The compositor may also use this information to adapt its behavior, e.g. choose an appropriate cursor image.

Parameters:	seat (`WlSeat`) – the `WlSeat` of the user event serial (uint) – the serial of the user event edges (uint) – which edge or corner is being dragged

set_max_size(width, height)¶

Request – opcode 7 (attached to Resource instance)

Set the maximum size

Set a maximum size for the window.

The client can specify a maximum size so that the compositor does not try to configure the window beyond this size.

The width and height arguments are in window geometry coordinates. See XdgSurface.set_window_geometry().

Values set in this way are double-buffered. They will get applied on the next commit.

The compositor can use this information to allow or disallow different states like maximize or fullscreen and draw accurate animations.

Similarly, a tiling window manager may use this information to place and resize client windows in a more effective way.

The client should not rely on the compositor to obey the maximum size. The compositor may decide to ignore the values set by the client and request a larger size.

If never set, or a value of zero in the request, means that the client has no expected maximum size in the given dimension. As a result, a client wishing to reset the maximum size to an unspecified state can use zero for width and height in the request.

Requesting a maximum size to be smaller than the minimum size of a surface is illegal and will result in a protocol error.

The width and height must be greater than or equal to zero. Using strictly negative values for width and height will result in a protocol error.

Parameters:	width (int) – height (int) –

set_min_size(width, height)¶

Request – opcode 8 (attached to Resource instance)

Set the minimum size

Set a minimum size for the window.

The client can specify a minimum size so that the compositor does not try to configure the window below this size.

The width and height arguments are in window geometry coordinates. See XdgSurface.set_window_geometry().

Values set in this way are double-buffered. They will get applied on the next commit.

The compositor can use this information to allow or disallow different states like maximize or fullscreen and draw accurate animations.

Similarly, a tiling window manager may use this information to place and resize client windows in a more effective way.

The client should not rely on the compositor to obey the minimum size. The compositor may decide to ignore the values set by the client and request a smaller size.

If never set, or a value of zero in the request, means that the client has no expected minimum size in the given dimension. As a result, a client wishing to reset the minimum size to an unspecified state can use zero for width and height in the request.

Requesting a minimum size to be larger than the maximum size of a surface is illegal and will result in a protocol error.

The width and height must be greater than or equal to zero. Using strictly negative values for width and height will result in a protocol error.

Parameters:	width (int) – height (int) –

set_maximized()¶

Request – opcode 9 (attached to Resource instance)

Maximize the window

Maximize the surface.

After requesting that the surface should be maximized, the compositor will respond by emitting a configure event. Whether this configure actually sets the window maximized is subject to compositor policies. The client must then update its content, drawing in the configured state. The client must also acknowledge the configure when committing the new content (see ack_configure).

It is up to the compositor to decide how and where to maximize the surface, for example which output and what region of the screen should be used.

If the surface was already maximized, the compositor will still emit a configure event with the “maximized” state.

If the surface is in a fullscreen state, this request has no direct effect. It may alter the state the surface is returned to when unmaximized unless overridden by the compositor.

unset_maximized()¶

Request – opcode 10 (attached to Resource instance)

Unmaximize the window

Unmaximize the surface.

After requesting that the surface should be unmaximized, the compositor will respond by emitting a configure event. Whether this actually un- maximizes the window is subject to compositor policies. If available and applicable, the compositor will include the window geometry dimensions the window had prior to being maximized in the configure event. The client must then update its content, drawing it in the configured state. The client must also acknowledge the configure when committing the new content (see ack_configure).

It is up to the compositor to position the surface after it was unmaximized; usually the position the surface had before maximizing, if applicable.

If the surface was already not maximized, the compositor will still emit a configure event without the “maximized” state.

If the surface is in a fullscreen state, this request has no direct effect. It may alter the state the surface is returned to when unmaximized unless overridden by the compositor.

set_fullscreen(output)¶

Request – opcode 11 (attached to Resource instance)

Set the window as fullscreen on an output

Make the surface fullscreen.

After requesting that the surface should be fullscreened, the compositor will respond by emitting a configure event. Whether the client is actually put into a fullscreen state is subject to compositor policies. The client must also acknowledge the configure when committing the new content (see ack_configure).

The output passed by the request indicates the client’s preference as to which display it should be set fullscreen on. If this value is NULL, it’s up to the compositor to choose which display will be used to map this surface.

If the surface doesn’t cover the whole output, the compositor will position the surface in the center of the output and compensate with with border fill covering the rest of the output. The content of the border fill is undefined, but should be assumed to be in some way that attempts to blend into the surrounding area (e.g. solid black).

If the fullscreened surface is not opaque, the compositor must make sure that other screen content not part of the same surface tree (made up of subsurfaces, popups or similarly coupled surfaces) are not visible below the fullscreened surface.

Parameters:	output (`WlOutput` or None) –

unset_fullscreen()¶

Request – opcode 12 (attached to Resource instance)

Unset the window as fullscreen

Make the surface no longer fullscreen.

After requesting that the surface should be unfullscreened, the compositor will respond by emitting a configure event. Whether this actually removes the fullscreen state of the client is subject to compositor policies.

Making a surface unfullscreen sets states for the surface based on the following: * the state(s) it may have had before becoming fullscreen * any state(s) decided by the compositor * any state(s) requested by the client while the surface was fullscreen

The compositor may include the previous window geometry dimensions in the configure event, if applicable.

The client must also acknowledge the configure when committing the new content (see ack_configure).

set_minimized()¶

Request – opcode 13 (attached to Resource instance)

Set the window as minimized

Request that the compositor minimize your surface. There is no way to know if the surface is currently minimized, nor is there any way to unset minimization on this surface.

If you are looking to throttle redrawing when minimized, please instead use the WlSurface.frame() event for this, as this will also work with live previews on windows in Alt-Tab, Expose or similar compositor features.

configure(width, height, states)¶

Event – opcode 0 (attached to Proxy instance)

Suggest a surface change

This configure event asks the client to resize its toplevel surface or to change its state. The configured state should not be applied immediately. See XdgSurface.configure() for details.

The width and height arguments specify a hint to the window about how its surface should be resized in window geometry coordinates. See set_window_geometry.

If the width or height arguments are zero, it means the client should decide its own window dimension. This may happen when the compositor needs to configure the state of the surface but doesn’t have any information about any previous or expected dimension.

The states listed in the event specify how the width/height arguments should be interpreted, and possibly how it should be drawn.

Clients must send an ack_configure in response to this event. See XdgSurface.configure() and XdgSurface.ack_configure() for details.

Parameters:	width (int) – height (int) – states (array) –

close()¶

Event – opcode 1 (attached to Proxy instance)

Surface wants to be closed

The close event is sent by the compositor when the user wants the surface to be closed. This should be equivalent to the user clicking the close button in client-side decorations, if your application has any.

This is only a request that the user intends to close the window. The client may choose to ignore this request, or show a dialog to ask the user to save their data, etc.

XdgPopup¶

class pywayland.protocol.xdg_shell.XdgPopup¶

Short-lived, popup surfaces for menus

A popup surface is a short-lived, temporary surface. It can be used to implement for example menus, popovers, tooltips and other similar user interface concepts.

A popup can be made to take an explicit grab. See XdgPopup.grab() for details.

When the popup is dismissed, a popup_done event will be sent out, and at the same time the surface will be unmapped. See the XdgPopup.popup_done() event for details.

Explicitly destroying the XdgPopup object will also dismiss the popup and unmap the surface. Clients that want to dismiss the popup when another surface of their own is clicked should dismiss the popup using the destroy request.

A newly created XdgPopup will be stacked on top of all previously created XdgPopup surfaces associated with the same XdgToplevel.

The parent of an XdgPopup must be mapped (see the XdgSurface description) before the XdgPopup itself.

The x and y arguments passed when creating the popup object specify where the top left of the popup should be placed, relative to the local surface coordinates of the parent surface. See XdgSurface.get_popup(). An XdgPopup must intersect with or be at least partially adjacent to its parent surface.

The client must call WlSurface.commit() on the corresponding WlSurface for the XdgPopup state to take effect.

destroy()¶

Request – opcode 0 (attached to Resource instance)

Remove XdgPopup interface

This destroys the popup. Explicitly destroying the XdgPopup object will also dismiss the popup, and unmap the surface.

If this XdgPopup is not the “topmost” popup, a protocol error will be sent.

grab(seat, serial)¶

Request – opcode 1 (attached to Resource instance)

Make the popup take an explicit grab

This request makes the created popup take an explicit grab. An explicit grab will be dismissed when the user dismisses the popup, or when the client destroys the XdgPopup. This can be done by the user clicking outside the surface, using the keyboard, or even locking the screen through closing the lid or a timeout.

If the compositor denies the grab, the popup will be immediately dismissed.

This request must be used in response to some sort of user action like a button press, key press, or touch down event. The serial number of the event should be passed as ‘serial’.

The parent of a grabbing popup must either be an XdgToplevel surface or another XdgPopup with an explicit grab. If the parent is another XdgPopup it means that the popups are nested, with this popup now being the topmost popup.

Nested popups must be destroyed in the reverse order they were created in, e.g. the only popup you are allowed to destroy at all times is the topmost one.

When compositors choose to dismiss a popup, they may dismiss every nested grabbing popup as well. When a compositor dismisses popups, it will follow the same dismissing order as required from the client.

The parent of a grabbing popup must either be another XdgPopup with an active explicit grab, or an XdgPopup or XdgToplevel, if there are no explicit grabs already taken.

If the topmost grabbing popup is destroyed, the grab will be returned to the parent of the popup, if that parent previously had an explicit grab.

If the parent is a grabbing popup which has already been dismissed, this popup will be immediately dismissed. If the parent is a popup that did not take an explicit grab, an error will be raised.

During a popup grab, the client owning the grab will receive pointer and touch events for all their surfaces as normal (similar to an “owner-events” grab in X11 parlance), while the top most grabbing popup will always have keyboard focus.

Parameters:	seat (`WlSeat`) – the `WlSeat` of the user event serial (uint) – the serial of the user event

configure(x, y, width, height)¶

Event – opcode 0 (attached to Proxy instance)

Configure the popup surface

This event asks the popup surface to configure itself given the configuration. The configured state should not be applied immediately. See XdgSurface.configure() for details.

The x and y arguments represent the position the popup was placed at given the XdgPositioner rule, relative to the upper left corner of the window geometry of the parent surface.

Parameters:	x (int) – x position relative to parent surface window geometry y (int) – y position relative to parent surface window geometry width (int) – window geometry width height (int) – window geometry height

popup_done()¶

Event – opcode 1 (attached to Proxy instance)

Popup interaction is done

The popup_done event is sent out when a popup is dismissed by the compositor. The client should destroy the XdgPopup object at this point.

XdgWmBase¶

class pywayland.protocol.xdg_shell.XdgWmBase¶

Create desktop-style surfaces

The XdgWmBase interface is exposed as a global object enabling clients to turn their wl_surfaces into windows in a desktop environment. It defines the basic functionality needed for clients and the compositor to create windows that can be dragged, resized, maximized, etc, as well as creating transient windows such as popup menus.

destroy()¶

Request – opcode 0 (attached to Resource instance)

Destroy XdgWmBase

Destroy this XdgWmBase object.

Destroying a bound XdgWmBase object while there are surfaces still alive created by this XdgWmBase object instance is illegal and will result in a protocol error.

create_positioner()¶

Request – opcode 1 (attached to Resource instance)

Create a positioner object

Create a positioner object. A positioner object is used to position surfaces relative to some parent surface. See the interface description and XdgSurface.get_popup() for details.

Returns:	`XdgPositioner`

get_xdg_surface(surface)¶

Request – opcode 2 (attached to Resource instance)

Create a shell surface from a surface

This creates an XdgSurface for the given surface. While XdgSurface itself is not a role, the corresponding surface may only be assigned a role extending XdgSurface, such as XdgToplevel or XdgPopup.

This creates an XdgSurface for the given surface. An XdgSurface is used as basis to define a role to a given surface, such as XdgToplevel or XdgPopup. It also manages functionality shared between XdgSurface based surface roles.

See the documentation of XdgSurface for more details about what an XdgSurface is and how it is used.

Parameters:	surface (`WlSurface`) –
Returns:	`XdgSurface`

pong(serial)¶

Request – opcode 3 (attached to Resource instance)

Respond to a ping event

A client must respond to a ping event with a pong request or the client may be deemed unresponsive. See XdgWmBase.ping().

Parameters:	serial (uint) – serial of the ping event

ping(serial)¶

Event – opcode 0 (attached to Proxy instance)

Check if the client is alive

The ping event asks the client if it’s still alive. Pass the serial specified in the event back to the compositor by sending a “pong” request back with the specified serial. See XdgWmBase.pong().

Compositors can use this to determine if the client is still alive. It’s unspecified what will happen if the client doesn’t respond to the ping request, or in what timeframe. Clients should try to respond in a reasonable amount of time.

A compositor is free to ping in any way it wants, but a client must always respond to any XdgWmBase object it created.

Parameters:	serial (uint) – pass this to the pong request

XdgPositioner¶

class pywayland.protocol.xdg_shell.XdgPositioner¶

Child surface positioner

The XdgPositioner provides a collection of rules for the placement of a child surface relative to a parent surface. Rules can be defined to ensure the child surface remains within the visible area’s borders, and to specify how the child surface changes its position, such as sliding along an axis, or flipping around a rectangle. These positioner-created rules are constrained by the requirement that a child surface must intersect with or be at least partially adjacent to its parent surface.

See the various requests for details about possible rules.

At the time of the request, the compositor makes a copy of the rules specified by the XdgPositioner. Thus, after the request is complete the XdgPositioner object can be destroyed or reused; further changes to the object will have no effect on previous usages.

For an XdgPositioner object to be considered complete, it must have a non-zero size set by set_size, and a non-zero anchor rectangle set by set_anchor_rect. Passing an incomplete XdgPositioner object when positioning a surface raises an error.

destroy()¶

Request – opcode 0 (attached to Resource instance)

Destroy the XdgPositioner object

Notify the compositor that the XdgPositioner will no longer be used.

set_size(width, height)¶

Request – opcode 1 (attached to Resource instance)

Set the size of the to-be positioned rectangle

Set the size of the surface that is to be positioned with the positioner object. The size is in surface-local coordinates and corresponds to the window geometry. See XdgSurface.set_window_geometry().

If a zero or negative size is set the invalid_input error is raised.

Parameters:	width (int) – width of positioned rectangle height (int) – height of positioned rectangle

set_anchor_rect(x, y, width, height)¶

Request – opcode 2 (attached to Resource instance)

Set the anchor rectangle within the parent surface

Specify the anchor rectangle within the parent surface that the child surface will be placed relative to. The rectangle is relative to the window geometry as defined by XdgSurface.set_window_geometry() of the parent surface.

When the XdgPositioner object is used to position a child surface, the anchor rectangle may not extend outside the window geometry of the positioned child’s parent surface.

If a negative size is set the invalid_input error is raised.

Parameters:	x (int) – x position of anchor rectangle y (int) – y position of anchor rectangle width (int) – width of anchor rectangle height (int) – height of anchor rectangle

set_anchor(anchor)¶

Request – opcode 3 (attached to Resource instance)

Set anchor rectangle anchor

Defines the anchor point for the anchor rectangle. The specified anchor is used derive an anchor point that the child surface will be positioned relative to. If a corner anchor is set (e.g. ‘top_left’ or ‘bottom_right’), the anchor point will be at the specified corner; otherwise, the derived anchor point will be centered on the specified edge, or in the center of the anchor rectangle if no edge is specified.

Parameters:	anchor (uint) – anchor

set_gravity(gravity)¶

Request – opcode 4 (attached to Resource instance)

Set child surface gravity

Defines in what direction a surface should be positioned, relative to the anchor point of the parent surface. If a corner gravity is specified (e.g. ‘bottom_right’ or ‘top_left’), then the child surface will be placed towards the specified gravity; otherwise, the child surface will be centered over the anchor point on any axis that had no gravity specified.

Parameters:	gravity (uint) – gravity direction

set_constraint_adjustment(constraint_adjustment)¶

Request – opcode 5 (attached to Resource instance)

Set the adjustment to be done when constrained

Specify how the window should be positioned if the originally intended position caused the surface to be constrained, meaning at least partially outside positioning boundaries set by the compositor. The adjustment is set by constructing a bitmask describing the adjustment to be made when the surface is constrained on that axis.

If no bit for one axis is set, the compositor will assume that the child surface should not change its position on that axis when constrained.

If more than one bit for one axis is set, the order of how adjustments are applied is specified in the corresponding adjustment descriptions.

The default adjustment is none.

Parameters:	constraint_adjustment (uint) – bit mask of constraint adjustments

set_offset(x, y)¶

Request – opcode 6 (attached to Resource instance)

Set surface position offset

Specify the surface position offset relative to the position of the anchor on the anchor rectangle and the anchor on the surface. For example if the anchor of the anchor rectangle is at (x, y), the surface has the gravity bottom|right, and the offset is (ox, oy), the calculated surface position will be (x + ox, y + oy). The offset position of the surface is the one used for constraint testing. See set_constraint_adjustment.

An example use case is placing a popup menu on top of a user interface element, while aligning the user interface element of the parent surface with some user interface element placed somewhere in the popup surface.

Parameters:	x (int) – surface position x offset y (int) – surface position y offset

XdgSurface¶

class pywayland.protocol.xdg_shell.XdgSurface¶

Desktop user interface surface base interface

An interface that may be implemented by a WlSurface, for implementations that provide a desktop-style user interface.

It provides a base set of functionality required to construct user interface elements requiring management by the compositor, such as toplevel windows, menus, etc. The types of functionality are split into XdgSurface roles.

Creating an XdgSurface does not set the role for a WlSurface. In order to map an XdgSurface, the client must create a role-specific object using, e.g., get_toplevel, get_popup. The WlSurface for any given XdgSurface can have at most one role, and may not be assigned any role not based on XdgSurface.

A role must be assigned before any other requests are made to the XdgSurface object.

The client must call WlSurface.commit() on the corresponding WlSurface for the XdgSurface state to take effect.

Creating an XdgSurface from a WlSurface which has a buffer attached or committed is a client error, and any attempts by a client to attach or manipulate a buffer prior to the first XdgSurface.configure() call must also be treated as errors.

Mapping an XdgSurface-based role surface is defined as making it possible for the surface to be shown by the compositor. Note that a mapped surface is not guaranteed to be visible once it is mapped.

For an XdgSurface to be mapped by the compositor, the following conditions must be met: (1) the client has assigned an XdgSurface-based role to the surface (2) the client has set and committed the XdgSurface state and the role-dependent state to the surface (3) the client has committed a buffer to the surface

A newly-unmapped surface is considered to have met condition (1) out of the 3 required conditions for mapping a surface if its role surface has not been destroyed.

destroy()¶

Request – opcode 0 (attached to Resource instance)

Destroy the XdgSurface

Destroy the XdgSurface object. An XdgSurface must only be destroyed after its role object has been destroyed.

get_toplevel()¶

Request – opcode 1 (attached to Resource instance)

Assign the XdgToplevel surface role

This creates an XdgToplevel object for the given XdgSurface and gives the associated WlSurface the XdgToplevel role.

See the documentation of XdgToplevel for more details about what an XdgToplevel is and how it is used.

Returns:	`XdgToplevel`

get_popup(parent, positioner)¶

Request – opcode 2 (attached to Resource instance)

Assign the XdgPopup surface role

This creates an XdgPopup object for the given XdgSurface and gives the associated WlSurface the XdgPopup role.

If null is passed as a parent, a parent surface must be specified using some other protocol, before committing the initial state.

See the documentation of XdgPopup for more details about what an XdgPopup is and how it is used.

Parameters:	parent (`XdgSurface` or None) – positioner (`XdgPositioner`) –
Returns:	`XdgPopup`

set_window_geometry(x, y, width, height)¶

Request – opcode 3 (attached to Resource instance)

Set the new window geometry

The window geometry of a surface is its “visible bounds” from the user’s perspective. Client-side decorations often have invisible portions like drop-shadows which should be ignored for the purposes of aligning, placing and constraining windows.

The window geometry is double buffered, and will be applied at the time WlSurface.commit() of the corresponding WlSurface is called.

When maintaining a position, the compositor should treat the (x, y) coordinate of the window geometry as the top left corner of the window. A client changing the (x, y) window geometry coordinate should in general not alter the position of the window.

Once the window geometry of the surface is set, it is not possible to unset it, and it will remain the same until set_window_geometry is called again, even if a new subsurface or buffer is attached.

If never set, the value is the full bounds of the surface, including any subsurfaces. This updates dynamically on every commit. This unset is meant for extremely simple clients.

The arguments are given in the surface-local coordinate space of the WlSurface associated with this XdgSurface.

The width and height must be greater than zero. Setting an invalid size will raise an error. When applied, the effective window geometry will be the set window geometry clamped to the bounding rectangle of the combined geometry of the surface of the XdgSurface and the associated subsurfaces.

Parameters:	x (int) – y (int) – width (int) – height (int) –

ack_configure(serial)¶

Request – opcode 4 (attached to Resource instance)

Ack a configure event

When a configure event is received, if a client commits the surface in response to the configure event, then the client must make an ack_configure request sometime before the commit request, passing along the serial of the configure event.

For instance, for toplevel surfaces the compositor might use this information to move a surface to the top left only when the client has drawn itself for the maximized or fullscreen state.

If the client receives multiple configure events before it can respond to one, it only has to ack the last configure event.

A client is not required to commit immediately after sending an ack_configure request - it may even ack_configure several times before its next surface commit.

A client may send multiple ack_configure requests before committing, but only the last request sent before a commit indicates which configure event the client really is responding to.

Parameters:	serial (uint) – the serial from the configure event

configure(serial)¶

Event – opcode 0 (attached to Proxy instance)

Suggest a surface change

The configure event marks the end of a configure sequence. A configure sequence is a set of one or more events configuring the state of the XdgSurface, including the final XdgSurface.configure() event.

Where applicable, XdgSurface surface roles will during a configure sequence extend this event as a latched state sent as events before the XdgSurface.configure() event. Such events should be considered to make up a set of atomically applied configuration states, where the XdgSurface.configure() commits the accumulated state.

Clients should arrange their surface for the new states, and then send an ack_configure request with the serial sent in this configure event at some point before committing the new surface.

If the client receives multiple configure events before it can respond to one, it is free to discard all but the last event it received.

Parameters:	serial (uint) – serial of the configure event