wayland::server::xdg_toplevel_t(3)

📦

version 1.0.1 · 10 versions

1.0.1 · ubuntu stonking (latest)
1.0.1-devman · nixos 26.05, nixpkgs unstable
1.0.0 · alpine 3.24
1.0.0 · ubuntu questing
1.0.1 · fedora 43
1.0.1 · fedora 44
1.0.0 · ubuntu noble
1.0.0 · debian bookworm
1.0.1 · ubuntu resolute
1.0.0 · debian trixie

Hey bestie 💖 you found wayland::server::xdg_toplevel_t(3) in the Wayland++ manual — part 1 of 3, and we're getting into the toplevel surface wrapper. Grab a strawberry 🍓 and let's go.

🌸 NAME 🌸

wayland::server::xdg_toplevel_t — toplevel surface. That's the whole vibe: this thing is the toplevel surface wrapper.

✨ SYNOPSIS ✨

First things first, the include:

#include <wayland-server-protocol-extra.hpp>

🫶 Public Member Functions 🫶

std::function< void()> & on_destroy () — destroy the xdg_toplevel
std::function< void(xdg_toplevel_t)> & on_set_parent () — set the parent of this surface
std::function< void(std::string)> & on_set_title () — set surface title
std::function< void(std::string)> & on_set_app_id () — set application ID
std::function< void(seat_t, uint32_t, int32_t, int32_t)> & on_show_window_menu () — show the window menu
std::function< void(seat_t, uint32_t)> & on_move () — start an interactive move
std::function< void(seat_t, uint32_t, xdg_toplevel_resize_edge)> & on_resize () — start an interactive resize
std::function< void(int32_t, int32_t)> & on_set_max_size () — set the maximum size
std::function< void(int32_t, int32_t)> & on_set_min_size () — set the minimum size
std::function< void()> & on_set_maximized () — maximize the window
std::function< void()> & on_unset_maximized () — unmaximize the window
std::function< void(output_t)> & on_set_fullscreen () — set the window as fullscreen on an output
std::function< void()> & on_unset_fullscreen () — unset the window as fullscreen
std::function< void()> & on_set_minimized () — set the window as minimized
void configure (int32_t width, int32_t height, array_t const &states, bool post=true) — suggest a surface change
void close (bool post=true) — surface wants to be closed
void configure_bounds (int32_t width, int32_t height, bool post=true) — recommended window geometry bounds
bool can_configure_bounds () const — Check whether the configure_bounds function is available with the currently bound version of the protocol.
void post_invalid_resize_edge (std::string const &msg) — Post error: provided value is not a valid variant of the resize_edge enum.
bool proxy_has_object () const — Check whether this wrapper actually wraps an object.
void post_no_memory () const
uint32_t get_id () const
client_t get_client () const
unsigned int get_version () const
std::string get_class ()

🎀 Static Public Attributes 🎀

static constexpr std::uint32_t configure_since_version = 1 — Minimum protocol version required for the configure function.
static constexpr std::uint32_t close_since_version = 1 — Minimum protocol version required for the close function.
static constexpr std::uint32_t configure_bounds_since_version = 4 — Minimum protocol version required for the configure_bounds function.

💖 Detailed Description 💖

Toplevel surface, periodt.

This interface defines an xdg_surface 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 xdg_toplevel 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 xdg_toplevel surface when it is unmapped. The xdg_toplevel returns to the state it had right after xdg_surface.get_toplevel. The client can re-map the toplevel by perfoming a commit without any buffer attached, waiting for a configure event and handling it as usual (see xdg_surface description).

⚠️ Attaching a null buffer to a toplevel unmaps the surface.

Definition at line 1301 of file wayland-server-protocol-extra.hpp.

🧚 Member Function Documentation 🧚

`bool xdg_toplevel_t::can_configure_bounds () const`

Check whether the configure_bounds function is available with the currently bound version of the protocol.

Definition at line 1351 of file wayland-server-protocol-extra.cpp.

`void xdg_toplevel_t::close (bool post = true)`

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.

Definition at line 1341 of file wayland-server-protocol-extra.cpp.

`void xdg_toplevel_t::configure (int32_t width, int32_t height, array_t const & states, bool post = true)`

suggest a surface change

Parameters:

width
height
states

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 xdg_surface.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 xdg_surface.configure and xdg_surface.ack_configure for details.

Definition at line 1336 of file wayland-server-protocol-extra.cpp.

`void xdg_toplevel_t::configure_bounds (int32_t width, int32_t height, bool post = true)`

recommended window geometry bounds

Parameters:

width
height

The configure_bounds event may be sent prior to a xdg_toplevel.configure event to communicate the bounds a window geometry size is recommended to constrain to.

The passed width and height are in surface coordinate space. If width and height are 0, it means bounds is unknown and equivalent to as if no configure_bounds event was ever sent for this surface.

The bounds can for example correspond to the size of a monitor excluding any panels or other shell components, so that a surface isn't created in a way that it cannot fit.

The bounds may change at any point, and in such a case, a new xdg_toplevel.configure_bounds will be sent, followed by xdg_toplevel.configure and xdg_surface.configure.

Definition at line 1346 of file wayland-server-protocol-extra.cpp.

`std::string wayland::server::resource_t::get_class () [inherited]`

Retrieve the interface name (class) of a resource object.

Returns: Interface name of the resource object.

`client_t wayland::server::resource_t::get_client () const [inherited]`

Get the associated client.

Returns: the client that owns the resource.

`uint32_t wayland::server::resource_t::get_id () const [inherited]`

Get the internal ID of the resource.

Returns: the internal ID of the resource.

`unsigned int wayland::server::resource_t::get_version () const [inherited]`

Get interface version.

Returns: Interface version this resource has been constructed with.

`std::function< void()> & xdg_toplevel_t::on_destroy ()`

destroy the xdg_toplevel. This request destroys the role surface and unmaps the surface; see "Unmapping" behavior in interface section for details.

Definition at line 1252 of file wayland-server-protocol-extra.cpp.

`std::function< void(seat_t, uint32_t)> & xdg_toplevel_t::on_move ()`

start an interactive move

Parameters:

seat — the wl_seat of the user event
serial — the serial of the user event

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 (wl_pointer, wl_touch, 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.

Definition at line 1282 of file wayland-server-protocol-extra.cpp.

`std::function< void(seat_t, uint32_t, xdg_toplevel_resize_edge)> & xdg_toplevel_t::on_resize ()`

start an interactive resize

Parameters:

seat — the wl_seat of the user event
serial — the serial of the user event
edges — which edge or corner is being dragged

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

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 (wl_pointer, wl_touch, 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. Values not matching a variant of the enum will cause a protocol error. 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.

Definition at line 1288 of file wayland-server-protocol-extra.cpp.

`std::function< void(std::string)> & xdg_toplevel_t::on_set_app_id ()`

set application ID

Parameters:

app_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.

Like, for D-Bus activatable apps, the app ID is the D-Bus service name — that's the whole vibe 💅

And the compositor shell is gonna try to group application surfaces together by their app ID, so best practice bestie: pick app IDs that match the basename of the app's .desktop file. Example time — "org.freedesktop.FooViewer" where the .desktop file is "org.freedesktop.FooViewer.desktop" ✨

Same as the other properties, a set_app_id request can totally be sent after the xdg_toplevel has been mapped, to update the property. No cap.

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

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

Definition at line 1270 of file wayland-server-protocol-extra.cpp.

`std::function< void(output_t)> & xdg_toplevel_t::on_set_fullscreen ()`

set the window as fullscreen on an output 🔥

Parameters

output

Make the surface fullscreen.

So after you request that the surface should be fullscreened, the compositor responds by emitting a configure event. Whether the client actually gets put into a fullscreen state is subject to compositor policies — so like, don't count on it, it's giving "we'll see" energy 😭

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 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. 👑

Definition at line 1318 of file wayland-server-protocol-extra.cpp.

`std::function< void(int32_t, int32_t)> & xdg_toplevel_t::on_set_max_size ()`

set the maximum size 📏

Parameters

width
height

Set a maximum size for the window.

The client can specify a maximum size so that the compositor doesn't try to configure the window beyond this size. Respect the ceiling, bestie.

The width and height arguments are in window geometry coordinates. See xdg_surface.set_window_geometry.

Values set this way are double-buffered — they get applied on the next commit. Classic.

The compositor can use this info to allow or disallow different states like maximize or fullscreen, and to 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. Rude, but legal 💀

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

Requesting a maximum size that's smaller than the minimum size of a surface is illegal and will result in a protocol error. Don't do it, fr fr 🙈

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. ⚠️

Definition at line 1294 of file wayland-server-protocol-extra.cpp.

`std::function< void()> & xdg_toplevel_t::on_set_maximized ()`

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's 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. Main character energy, honestly.

If the surface was already maximized, the compositor will still emit a configure event with the "maximized" state. Consistency icon.

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. iykyk.

Definition at line 1306 of file wayland-server-protocol-extra.cpp.

`std::function< void(int32_t, int32_t)> & xdg_toplevel_t::on_set_min_size ()`

set the minimum size 📐

Parameters

width
height

Set a minimum size for the window.

The client can specify a minimum size so that the compositor doesn't try to configure the window below this size. Gotta have standards 💅

The width and height arguments are in window geometry coordinates. See xdg_surface.set_window_geometry.

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

The compositor can use this info 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 the client has no expected minimum size in the given dimension. So 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 that's larger than the maximum size of a surface is illegal and will result in a protocol error. Bestie, no 🫶

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.

Definition at line 1300 of file wayland-server-protocol-extra.cpp.

`std::function< void()> & xdg_toplevel_t::on_set_minimized ()`

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. Yeah. It's a one-way trip, genuinely.

If you're looking to throttle redrawing when minimized, please instead use the wl_surface.frame event for this, as this will also work with live previews on windows in Alt-Tab, Expose or similar compositor features. Do that instead, bestie, it ate. ✨

Definition at line 1330 of file wayland-server-protocol-extra.cpp.

`std::function< void(xdg_toplevel_t)> & xdg_toplevel_t::on_set_parent ()`

set the parent of this surface 🎀

Parameters

parent

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. Family hierarchy, but make it Windows.

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. Lowkey chill about it.

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. The lore goes deep 🌀

Definition at line 1258 of file wayland-server-protocol-extra.cpp.

`std::function< void(std::string)> & xdg_toplevel_t::on_set_title ()`

set surface title 🏷️

Parameters

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. So like, make it good, it's your whole brand.

The string must be encoded in UTF-8. No cap. 💖

Definition at line 1264 of file wayland-server-protocol-extra.cpp.

`std::function< void(seat_t, uint32_t, int32_t, int32_t)> & xdg_toplevel_t::on_show_window_menu ()`

show the window menu 🍓

Parameters

seat — the wl_seat of the user event
serial — the serial of the user event
x — the x position to pop up the window menu at
y — the y position to pop up the window menu at

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. Obsessed with that, honestly.

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 — surprise mechanics 😭

This request must be used in response to some sort of user action like a button press, key press, or touch down event. Don't just fire it off randomly, bestie.

Definition at line 1276 of file wayland-server-protocol-extra.cpp.

`std::function< void()> & xdg_toplevel_t::on_unset_fullscreen ()`

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).

Definition at line 1324 of file wayland-server-protocol-extra.cpp.

`std::function< void()> & xdg_toplevel_t::on_unset_maximized ()`

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's up to the compositor to position the surface after it was unmaximized — usually the position the surface had before maximizing, if applicable. Muscle memory, honestly.

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.

Definition at line 1312 of file wayland-server-protocol-extra.cpp.

void xdg_toplevel_t::post_invalid_resize_edge (std::string const & msg) — throws the error “provided value is not a valid variant of the resize_edge enum” at the client, bestie. You passed a resize edge that straight-up isn't a thing 😭.

Definition at line 1356 of file wayland-server-protocol-extra.cpp.

void wayland::server::resource_t::post_no_memory () const [inherited] — posts the “not enough memory” error over to the client 🫠.

So like, if the compositor doesn't have enough memory to actually do whatever the client just asked for, this is the function you call to let the client know what's up. Very “hey bestie, I'm broke rn” energy.

bool wayland::server::resource_t::proxy_has_object () const [inherited] — vibe check on your wrapper: does it actually wrap an object or not? 👀

Returns

true if there's an underlying object, false if this wrapper is empty. That's it. That's the whole function. Iconic honestly.

🧮 Member Data Documentation 🧮

std::uint32_t wayland::server::xdg_toplevel_t::close_since_version = 1 [static], [constexpr] — the minimum protocol version required for the close function. Like the entry fee for close ✨.

Definition at line 1751 of file wayland-server-protocol-extra.hpp.

std::uint32_t wayland::server::xdg_toplevel_t::configure_bounds_since_version = 4 [static], [constexpr] — minimum protocol version required for the configure_bounds function. Version 4 specifically, no cap 🫶.

Definition at line 1778 of file wayland-server-protocol-extra.hpp.

std::uint32_t wayland::server::xdg_toplevel_t::configure_since_version = 1 [static], [constexpr] — minimum protocol version required for the configure function. Starts at good ol' version 1 💅.

Definition at line 1733 of file wayland-server-protocol-extra.hpp.

✍️ Author ✍️

Generated automatically by Doxygen for Wayland++ from the source code. Not a human, not a girlie, just vibes and parsers 🤖💖.

okay that's the whole page bestie, you made it to the end 🎀🌸 the footnote energy is: Version 1.0.1, dated Fri Mar 27 2026 — that's your source/version and your date, and honestly? may your protocol versions always be compatible and your wrappers never empty 🦋✨💜

📦 where this page comes from

ubuntu stonking: waylandpp-dev 1.0.1-2 · BSD-2-Clause
💖 girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on 2026-11-06: a language model's rewrite of the original, under its terms