xcb_randr_cha...tput_property(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_change_output_property β€” bestie's guide to the XCB Requests manual πŸ’…

okay so. this is a page from XCB Requests (that's the manual name, mwah) and its whole vibe is "change the property of an output in RandR". the official description after the dash is literally nothing, so we're not gonna invent one, bestie. we keep it real. ✨


✨ NAME ✨

xcb_randr_change_output_property -

no cap, that trailing dash is just sitting there with no description. iconic behavior honestly. πŸ’€

πŸ¦‹ SYNOPSIS πŸ¦‹

#include <xcb/randr.h>

πŸ’– Request function πŸ’–

xcb_void_cookie_t
       xcb_randr_change_output_property(xcb_connection_t *conn,
       xcb_randr_output_t output, xcb_atom_t property, xcb_atom_t type,
       uint8_t format, uint8_t mode, uint32_t num_units, const
       void *data);

πŸŽ€ REQUEST ARGUMENTS πŸŽ€

the way these all say the same thing... okay anyway, here's the lineup:

  • conn β€” the XCB connection to X11. your little hotline to the server, periodt. πŸ”₯
  • output β€” TODO: NOT YET DOCUMENTED.
  • property β€” TODO: NOT YET DOCUMENTED.
  • type β€” TODO: NOT YET DOCUMENTED.
  • format β€” TODO: NOT YET DOCUMENTED.
  • mode β€” TODO: NOT YET DOCUMENTED.
  • num_units β€” TODO: NOT YET DOCUMENTED.
  • data β€” TODO: NOT YET DOCUMENTED.
not me having to tell you that seven of these are still unwritten in the actual source docs 😭 that's just what it says, i don't make the rules.

🌈 DESCRIPTION 🌈

...yeah. there's nothing here. the section exists and it is empty, and we respect it. no filler, no guessing, no making stuff up about how this function behaves. if you wanna know, go read the code, bestie. 🫢


πŸ’œ RETURN VALUE πŸ’œ

it hands you back an xcb_void_cookie_t. and here's the tea: any errors have to be handled in the event loop, not right here.

if you'd rather deal with errors directly using xcb_request_check instead, then use xcb_randr_change_output_property_checked. see xcb-requests(3) for the full details. πŸ’…


πŸ’€ ERRORS πŸ’€

this request never generates any errors. zero. none. clean sheet. slay. ✨


⭐ SEE ALSO ⭐

this section is blank in the original. nothing listed. no cap. (yes i checked. twice.) πŸ™ˆ

πŸ‘‘ AUTHOR πŸ‘‘

generated from randr.xml. if you've got corrections or improvements, hit up xcb@lists.freedesktop.org β€” they'd love to hear from you, fr fr. πŸ“


and that's the whole page, bestie!! 🌸 this was shipped as part of X Version 11, libxcb 1.17.0, so if you're citing it, that's the era we're living in. main character energy only. take care of your outputs, hydrate, and may your properties always change exactly how you meant them to πŸ’–βœ¨πŸ¦‹