XCB_RANDR_CONFIGURE_OUTPUT_PROPERTY_CHECKED(3)

📦
version 1.17.0 · 4 versions
, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, centos-stream 10, debian trixie, fedora 43, fedora 44, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking

✨ xcb_randr_configure_output_property ✨

okay bestie, welcome to the <xcb/randr.h> cinematic universe 💖 this one lives in the manual page for xcb_randr_configure_output_property, a lil XCB request from the RandR corner of town. it's giving "i configure an output property and i say nothing else" energy, and honestly? iconic. 👑

🌸 NAME 🌸

xcb_randr_configure_output_property — ...and that's literally it, the description field is empty, the mystery is the brand 🫶

🦋 SYNOPSIS 🦋

#include <xcb/randr.h>

✨ Request function ✨

xcb_void_cookie_t
       xcb_randr_configure_output_property(xcb_connection_t *conn,
       xcb_randr_output_t output, xcb_atom_t property, uint8_t pending,
       uint8_t range, uint32_t values_len, const int32_t *values);

like look at that signature. seven whole arguments. main character behaviour fr fr 💅

🎀 REQUEST ARGUMENTS 🎀

  • conn — the XCB connection to X11. your lil hotline to the server, the group chat you're posting in 📞
  • output — TODO: NOT YET DOCUMENTED. no cap, that's literally what the page says, i'm not gatekeeping anything from you 🙈
  • property — TODO: NOT YET DOCUMENTED. same situation bestie, the lore is unfinished 😭
  • pending — TODO: NOT YET DOCUMENTED. mysterious. enigmatic. lowkey thriving ✨
  • range — TODO: NOT YET DOCUMENTED. the range of what?? we simply do not know 🦋
  • values_len — TODO: NOT YET DOCUMENTED. presumably the length of something but the docs said "not today" 💀
  • values — TODO: NOT YET DOCUMENTED. a const int32_t *, so like, a pointer to ints, and that's all we're getting 🍓
not me reading this section expecting answers and getting seven TODOs instead 😭 the documentation said "figure it out yourself, queen"

🌈 DESCRIPTION 🌈

genuinely nothing here.</purole>

empty. a blank canvas. the void. we love a minimalist moment 💜

👑 RETURN VALUE 👑

it hands you back an xcb_void_cookie_t. cute, right? yeah — except errors (if any) have to be handled in the event loop. so you don't get to ignore them, bestie, you gotta go catch them later like they're a situationship 🔥

if you'd rather handle errors directly with xcb_request_check instead, then use xcb_randr_configure_output_property_checked — that's the checked twin, the responsible sibling, the one who does their homework 📚

see xcb-requests(3) for details, iykyk 🫶

💀 ERRORS 💀

This request does never generate any errors.

like... none. zero. not a single one. the calmest request in the whole building 🧚✨ flawless, no notes, we stan an unproblematic fave

🌸 SEE ALSO 🌸

nothing listed. the see-also section is a quiet lil void, and honestly? respect. sometimes the vibe is silence. 🦋

💖 AUTHOR 💖

Generated from randr.xml. 🎀

Contact xcb@lists.freedesktop.org for corrections and improvements — so if you spot something sus, tell the humans, they're lovely and they fix things 💌

and that's the whole page, babe! this was X Version 11, libxcb 1.17.0, and yes it came from the XCB requests corner of the manual, mwah 💋 slay, go configure something ✨

📦 where this page comes from