xcb_randr_set_crtc_config(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_set_crtc_config πŸ’–

okay bestie, we're diving into the XCB Requests corner of the manual, page xcb_randr_set_crtc_config(3), and honestly? this one is giving "screen glow-up" energy. it's how you tell the X server how to set up a CRTC. slay.


🌸 NAME 🌸

xcb_randr_set_crtc_config β€” (yeah, the original just leaves this blank, no cap, not a single word of description. iconic of them honestly.) πŸ’…


✨ SYNOPSIS ✨

first up, the include, as always:

#include <xcb/randr.h>

πŸŽ€ Request function πŸŽ€

xcb_randr_set_crtc_config_cookie_t
       xcb_randr_set_crtc_config(xcb_connection_t *conn,
       xcb_randr_crtc_t crtc, xcb_timestamp_t timestamp,
       xcb_timestamp_t config_timestamp, int16_t x, int16_t y,
       xcb_randr_mode_t mode, uint16_t rotation, uint32_t outputs_len,
       const xcb_randr_output_t *outputs);

πŸŽ€ Reply datastructure πŸŽ€

typedef struct xcb_randr_set_crtc_config_reply_t {
    uint8_t         response_type;
    uint8_t         status;
    uint16_t        sequence;
    uint32_t        length;
    xcb_timestamp_t timestamp;
    uint8_t         pad0[20];
} xcb_randr_set_crtc_config_reply_t;

πŸŽ€ Reply function πŸŽ€

xcb_randr_set_crtc_config_reply_t
       *xcb_randr_set_crtc_config_reply(xcb_connection_t *conn,
       xcb_randr_set_crtc_config_cookie_t cookie,
       xcb_generic_error_t **e);

πŸ¦‹ REQUEST ARGUMENTS πŸ¦‹

  • conn β€” your XCB connection to X11. the main character, the plug, the whole reason we're here. 🫢
  • crtc β€” TODO: NOT YET DOCUMENTED. (the docs really said "figure it out bestie" 😭)
  • timestamp β€” TODO: NOT YET DOCUMENTED.
  • config_timestamp β€” TODO: NOT YET DOCUMENTED.
  • x β€” TODO: NOT YET DOCUMENTED.
  • y β€” TODO: NOT YET DOCUMENTED.
  • mode β€” TODO: NOT YET DOCUMENTED.
  • rotation β€” TODO: NOT YET DOCUMENTED.
  • outputs_len β€” TODO: NOT YET DOCUMENTED.
  • outputs β€” TODO: NOT YET DOCUMENTED.

like... they left the whole menu blank, we're ordering blind, but we still copy every line exactly, periodt. πŸ’€


🌈 REPLY FIELDS 🌈

  • response_type β€” the type of this reply, and in this case it's XCB_RANDR_SET_CRTC_CONFIG. this field is also chillin' inside xcb_generic_reply_t, so you can use it to tell your replies apart from each other. lowkey the social security number of replies.
  • sequence β€” the sequence number of the last request processed by the X11 server. it's giving "receipt number". 🧾
  • length β€” the length of the reply, in words (and a word is 4 bytes, keep that in your notes bestie). ✨
  • status β€” TODO: NOT YET DOCUMENTED.
  • timestamp β€” TODO: NOT YET DOCUMENTED.

πŸ’œ DESCRIPTION πŸ’œ

(the original leaves this section completely empty. yes, truly. nothing. void. the silence is deafening. 🌸)


πŸ‘‘ RETURN VALUE πŸ‘‘

it hands you back an xcb_randr_set_crtc_config_cookie_t. πŸͺ

errors? you gotta handle those yourself when you call the reply function xcb_randr_set_crtc_config_reply.

and if you'd rather catch errors in the event loop instead β€” very valid, very "I'll deal with it when it arrives" of you β€” use xcb_randr_set_crtc_config_unchecked. peep xcb-requests(3) for all the deets. πŸ’…


πŸ’– ERRORS πŸ’–

this request does never generate any errors. zero. none. clean run, no drama, we love a low-maintenance request. ✨

πŸ“ SEE ALSO πŸ“

(the original section is empty, so there's literally nothing to reference here. we respect the emptiness.)


🌟 AUTHOR 🌟

Generated from randr.xml. πŸ“ Contact xcb@lists.freedesktop.org for corrections and improvements β€” they're literally asking for your notes, so don't be shy.


and that's the whole page, bestie!! πŸŽ€ this gorgeous little number comes to you from X Version 11, libxcb 1.17.0, and it's filed under xcb_randr_set_crtc_config(3). go configure a CRTC and be iconic about it. mwah. πŸ’‹πŸ’…βœ¨