wayland::server::output_t(3)

📦
version 1.0.1 · 11 versions
, in ubuntu stonking

🎀 NAME: wayland::server::output_t(3) 🎀

okay bestie, this page is from the Wayland++ manual, and the main character is wayland::server::output_t — a compositor output region. 💅

✨ SYNOPSIS ✨

#include <wayland-server-protocol.hpp>

💖 Public Member Functions 💖

  • std::function< void()> & on_release () — release the output object. 🫶
  • void geometry (int32_t x, int32_t y, int32_t physical_width, int32_t physical_height, output_subpixel const &subpixel, std::string const &make, std::string const &model, output_transform const &transform, bool post=true) — properties of the output. lowkey the whole physical-vibe package. 🦋
  • void mode (output_mode const &flags, int32_t width, int32_t height, int32_t refresh, bool post=true) — advertise available modes for the output. ✨
  • void done (bool post=true) — sent all information about output. periodt, that's the wrap-up. 💅
  • bool can_done () const — Check whether the done function is available with the currently bound version of the protocol. 🔍
  • void scale (int32_t factor, bool post=true) — output scaling properties. slay, but make it bigger or smaller. 🎀
  • bool can_scale () const — Check whether the scale function is available with the currently bound version of the protocol. 🔍
  • void name (std::string const &name, bool post=true) — name of this output. give the monitor its government name. 👑
  • bool can_name () const — Check whether the name function is available with the currently bound version of the protocol. 🔍
  • void description (std::string const &description, bool post=true) — human-readable description of this output. no cap, it's the friendly little bio. 🌸
  • bool can_description () const — Check whether the description function is available with the currently bound version of the protocol. 🔍
  • bool proxy_has_object () const — Check whether this wrapper actually wraps an object. vibe check for the wrapper itself. 🫶
  • void post_no_memory () const — the manual gives no extra one-liner here, just the signature. respect the mystery. 💀
  • uint32_t get_id () const — signature only in the source, no extra description. 🍓
  • client_t get_client () const — signature only in the source, no extra description. 🍓
  • unsigned int get_version () const — signature only in the source, no extra description. 🍓
  • std::string get_class () — signature only in the source, no extra description. 🍓

🦋 Static Public Attributes 🦋

  • static constexpr std::uint32_t geometry_since_version = 1 — Minimum protocol version required for the geometry function. 🧚
  • static constexpr std::uint32_t mode_since_version = 1 — Minimum protocol version required for the mode function. 🧚
  • static constexpr std::uint32_t done_since_version = 2 — Minimum protocol version required for the done function. 🧚
  • static constexpr std::uint32_t scale_since_version = 2 — Minimum protocol version required for the scale function. 🧚
  • static constexpr std::uint32_t name_since_version = 4 — Minimum protocol version required for the name function. 🧚
  • static constexpr std::uint32_t description_since_version = 4 — Minimum protocol version required for the description function. 🧚

🔥 Detailed Description 🔥

okay so here's the lore, bestie: an output describes part of the compositor geometry. The compositor works in the 'compositor coordinate system' and an output corresponds to a rectangular area in that space that is actually visible. This typically corresponds to a monitor that displays part of the compositor space. This object is published as global during start up, or when a monitor is hotplugged. 🌈

Definition at line 3706 of file wayland-server-protocol.hpp. 💜

💖 MEMBER FUNCTION DOCUMENTATION 💖

okay bestie, this is the part where we go through literally every single method one by one. buckle up 🎀

bool output_t::can_description () const

vibe check: is the description function even available on the protocol version you're currently bound to? that's it, that's the whole function. returns a bool, no cap.

Definition at line 2993 of file wayland-server-protocol.cpp.

bool output_t::can_done () const

same energy, different event — checks whether the done function is available with the currently bound version of the protocol. ✨

Definition at line 2963 of file wayland-server-protocol.cpp.

bool output_t::can_name () const

you guessed it — is name available on your currently bound protocol version? yes/no, icon behavior. 💅

Definition at line 2983 of file wayland-server-protocol.cpp.

bool output_t::can_scale () const

and this one checks whether scale is available with the currently bound version of the protocol. the little quartet of can_ functions, we love a consistent queen 👑

Definition at line 2973 of file wayland-server-protocol.cpp.

void output_t::description (std::string const & description, bool post = true)

the human-readable description of this output 🏷️

Parameters

  • description — output description

so like — many compositors can produce human-readable descriptions of their outputs, and the client may want to know that description too, e.g. for output selection purposes.

the description is a UTF-8 string with no convention defined for its contents. and heads up: it is not guaranteed to be unique among all wl_output globals. examples might include 'Foocorp 11" Display' or 'Virtual X11 output via :1'.

the description event is sent after binding the output object and whenever the description changes. it's optional, tho — it may not be sent at all 🙈

oh and the description event will be followed by a done event.

Definition at line 2988 of file wayland-server-protocol.cpp.

void output_t::done (bool post = true)

"sent all information about output" — this event is sent after all other properties have been sent after binding to the output object, and after any other property changes done after that. the whole point? it lets changes to the output properties be seen as atomic, even if they happen via multiple events. main character synchronization moment ✨

Definition at line 2958 of file wayland-server-protocol.cpp.

void output_t::geometry (int32_t x, int32_t y, int32_t physical_width, int32_t physical_height, output_subpixel const & subpixel, std::string const & make, std::string const & model, output_transform const & transform, bool post = true)

the properties of the output — the whole glow-up package.

Parameters

  • x — x position within the global compositor space
  • y — y position within the global compositor space
  • physical_width — width in millimeters of the output
  • physical_height — height in millimeters of the output
  • subpixel — subpixel orientation of the output
  • make — textual description of the manufacturer
  • model — textual description of the model
  • transform — transform that maps framebuffer to output

the geometry event describes geometric properties of the output. it's sent when binding to the output object and whenever any of the properties change.

the physical size can be set to zero if it doesn't make sense for this output (e.g. for projectors or virtual outputs). zero is valid, bestie, don't panic 💀

the geometry event will be followed by a done event (starting from version 2).

Note: wl_output only advertises partial information about the output position and identification. some compositors — for instance those not implementing a desktop-style output layout, or those exposing virtual outputs — might fake this information. instead of using x and y, clients should use xdg_output.logical_position. instead of using make and model, clients should use name and description. iykyk 🫶

Definition at line 2948 of file wayland-server-protocol.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.

inherited behavior, still iconic 💜

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.

void output_t::mode (output_mode const & flags, int32_t width, int32_t height, int32_t refresh, bool post = true)

advertise the available modes for the output 📺

Parameters

  • flags — bitfield of mode flags
  • width — width of the mode in hardware units
  • height — height of the mode in hardware units
  • refresh — vertical refresh rate in mHz

the mode event describes an available mode for the output.

it's sent when binding to the output object, and there will always be one mode — the current mode. the event gets sent again if an output changes mode, for the mode that is now current. in other words: the current mode is always the last mode that was received with the current flag set. periodt 💅

non-current modes are deprecated. a compositor can decide to only advertise the current mode and never send other modes. clients should not rely on non-current modes. like, don't build your whole personality on them, fr.

the size of a mode is given in physical hardware units of the output device — which is not necessarily the same as the output size in the global compositor space. for instance, the output may be scaled (as described in wl_output.scale) or transformed (as described in wl_output.transform). clients willing to retrieve the output size in the global compositor space should use xdg_output.logical_size instead.

the vertical refresh rate can be set to zero if it doesn't make sense for this output (e.g. for virtual outputs).

the mode event will be followed by a done event (starting from version 2).

clients should not use the refresh rate to schedule frames. instead, they should use the wl_surface.frame event or the presentation-time protocol. that's the assignment, bestie 🦋

Note: this information is not always meaningful for all outputs. some compositors, such as those exposing virtual outputs, might fake the refresh rate or the size. 🙈

Definition at line 2953 of file wayland-server-protocol.cpp.

void output_t::name (std::string const & name, bool post = true)

the name of this output 🏷️

Parameters

  • name — output name

many compositors will assign user-friendly names to their outputs, show them to the user, allow the user to refer to an output, etc. the client may wish to know this name too so it can offer the user similar behaviors.

the name is a UTF-8 string with no convention defined for its contents. each name is unique among all wl_output globals, but the name is only guaranteed to be unique for the compositor instance.

the same output name is used for all clients for a given wl_output global. so the name can be shared across processes to refer to a specific wl_output global. we love a consistent identifier ✨

the name is not guaranteed to be persistent across sessions, so it cannot be used to reliably identify an output in e.g. configuration files. hard truth, sorry 😭

examples of names include 'HDMI-A-1', 'WL-1', 'X11-1', etc. however, do not assume the name is a reflection of an underlying DRM connector, X11 connection, etc. it's giving "just a name," not a whole autobiography.

the name event is sent after binding the output object. this event is only sent once per output object, and the name does not change over the lifetime of the wl_output global.

compositors may re-use the same output name if the wl_output global is destroyed and re-created later. compositors should avoid re-using the same name if possible 🫶

the name event will be followed by a done event.

Definition at line 2978 of file wayland-server-protocol.cpp.

std::function< void()> & output_t::on_release ()

release the output object. using this request, a client can tell the server that it is not going to use the output object anymore. it's the polite goodbye, the "i'm leaving the group chat" of events 👋

Definition at line 2942 of file wayland-server-protocol.cpp.

void wayland::server::resource_t::post_no_memory () const [inherited]

post a "not enough memory" error to the client.

if the compositor doesn't have enough memory to fulfill a certain request of the client, this function can be called to notify the client of this circumstance. it's the "💀 ran out of RAM" announcement, inherited and ready to go.

bool wayland::server::resource_t::proxy_has_object () const [inherited]

check whether this wrapper actually wraps an object.

Returns

true if there is an underlying object, false if this wrapper is empty.

like checking if there's actually someone in the group chat or if it's just you and a dead group. inherited 🔥

void output_t::scale (int32_t factor, bool post = true)

output scaling properties 🔍

Parameters

  • factor — scaling factor of output

this event contains scaling geometry information that is not in the geometry event. it may be sent after binding the output object, or if the output scale changes later. if it is not sent, the client should assume a scale of 1.

a scale larger than 1 means the compositor will automatically scale surface buffers by this amount when rendering. this is used for very high resolution displays where applications rendering at the native resolution would be too small to be legible. tiny text era: canceled 🎀

the intention is that scaling-aware clients track the current output of a surface, and if it's on a scaled output it should use wl_surface.set_buffer_scale with the scale of the output. that way the compositor can avoid scaling the surface, and the client can supply a higher detail image. everybody wins, flawless victory ✨

the scale event will be followed by a done event.

Definition at line 2968 of file wayland-server-protocol.cpp.

🎀 MEMBER DATA DOCUMENTATION 🎀

these are the static constexpr besties that tell you the minimum protocol version for each function. lowkey the most useful little numbers in the whole file 💅

std::uint32_t wayland::server::output_t::description_since_version = 4 [static], [constexpr]

minimum protocol version required for the description function.

Definition at line 3944 of file wayland-server-protocol.hpp.

std::uint32_t wayland::server::output_t::done_since_version = 2 [static], [constexpr]

minimum protocol version required for the done function.

Definition at line 3834 of file wayland-server-protocol.hpp.

std::uint32_t wayland::server::output_t::geometry_since_version = 1 [static], [constexpr]

minimum protocol version required for the geometry function. version 1, the original icon 👑

Definition at line 3772 of file wayland-server-protocol.hpp.

std::uint32_t wayland::server::output_t::mode_since_version = 1 [static], [constexpr]

minimum protocol version required for the mode function.

Definition at line 3819 of file wayland-server-protocol.hpp.

std::uint32_t wayland::server::output_t::name_since_version = 4 [static], [constexpr]

minimum protocol version required for the name function.

Definition at line 3914 of file wayland-server-protocol.hpp.

std::uint32_t wayland::server::output_t::scale_since_version = 2 [static], [constexpr]

minimum protocol version required for the scale function.

Definition at line 3870 of file wayland-server-protocol.hpp.

🌈 AUTHOR 🌈

generated automatically by Doxygen for Wayland++ from the source code. not a human wrote this, it's a whole robot situation 🤖✨

aaaand that's the whole page bestie, you ate that 💅💖 this totes came from Version 1.0.1, dated Fri Mar 27 2026 13:15:0 — go forth and bind your outputs responsibly, mwah 🫶🎀🦋

📦 where this page comes from