xcb_randr_get...urces_current(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_get...urces_current β€” from the XCB Requests manual, bestie πŸ’–

okay so. we're diving into xcb_randr_get_screen_resources_current(3) and honestly? it's giving "quietly powerful". no cap. let's get into it 🫢


✨ NAME ✨

xcb_randr_get_screen_resources_current -

(yes bestie, the description after the dash is literally empty in the original. iconic of it, honestly. nothing to add, nothing to take away πŸ’…)


✨ SYNOPSIS ✨

#include <xcb/randr.h>

🌸 Request function

xcb_randr_get_screen_resources_current_cookie_t
       xcb_randr_get_screen_resources_current(xcb_connection_t *conn,
       xcb_window_t window);

🌸 Reply datastructure

typedef struct xcb_randr_get_screen_resources_current_reply_t {
    uint8_t         response_type;
    uint8_t         pad0;
    uint16_t        sequence;
    uint32_t        length;
    xcb_timestamp_t timestamp;
    xcb_timestamp_t config_timestamp;
    uint16_t        num_crtcs;
    uint16_t        num_outputs;
    uint16_t        num_modes;
    uint16_t        names_len;
    uint8_t         pad1[8];
} xcb_randr_get_screen_resources_current_reply_t;

🌸 Reply function

xcb_randr_get_screen_resources_current_reply_t
       *xcb_randr_get_screen_resources_current_reply(xcb_connection_t *conn,
       xcb_randr_get_screen_resources_current_cookie_t cookie,
       xcb_generic_error_t **e);

🌸 Reply accessors

like, the whole little squad of getters. every single one, bestie:

xcb_randr_crtc_t *xcb_randr_get_screen_resources_current_crtcs(const
       xcb_randr_get_screen_resources_current_request_t *reply);
int xcb_randr_get_screen_resources_current_crtcs_length(const
       xcb_randr_get_screen_resources_current_reply_t *reply);
xcb_generic_iterator_t
       xcb_randr_get_screen_resources_current_crtcs_end(const
       xcb_randr_get_screen_resources_current_reply_t *reply);
xcb_randr_output_t *xcb_randr_get_screen_resources_current_outputs(const
       xcb_randr_get_screen_resources_current_request_t *reply);
int xcb_randr_get_screen_resources_current_outputs_length(const
       xcb_randr_get_screen_resources_current_reply_t *reply);
xcb_generic_iterator_t
       xcb_randr_get_screen_resources_current_outputs_end(const
       xcb_randr_get_screen_resources_current_reply_t *reply);
xcb_randr_mode_info_t
       *xcb_randr_get_screen_resources_current_modes(const
       xcb_randr_get_screen_resources_current_request_t *reply);
int xcb_randr_get_screen_resources_current_modes_length(const
       xcb_randr_get_screen_resources_current_reply_t *reply);
xcb_randr_mode_info_iterator_t
       xcb_randr_get_screen_resources_current_modes_iterator(const
       xcb_randr_get_screen_resources_current_reply_t *reply);
uint8_t *xcb_randr_get_screen_resources_current_names(const
       xcb_randr_get_screen_resources_current_request_t *reply);
int xcb_randr_get_screen_resources_current_names_length(const
       xcb_randr_get_screen_resources_current_reply_t *reply);
xcb_generic_iterator_t
       xcb_randr_get_screen_resources_current_names_end(const
       xcb_randr_get_screen_resources_current_reply_t *reply);

🌈 REQUEST ARGUMENTS 🌈

  • conn β€” your XCB connection to X11. the whole little lifeline, fr fr. πŸ’«
  • window β€” TODO: NOT YET DOCUMENTED. (not me being the messenger here, the docs literally say that 😭 we keep it 100.)

πŸ¦‹ REPLY FIELDS πŸ¦‹

  • response_type β€” the type of this reply, in this case XCB_RANDR_GET_SCREEN_RESOURCES_CURRENT. this field is also present in the xcb_generic_reply_t and can be used to tell replies apart from each other. it's giving "hey it's me, your reply" πŸ’…
  • sequence β€” the sequence number of the last request processed by the X11 server. the receipts, basically. 🧾
  • length β€” the length of the reply, in words (a word is 4 bytes). math girlies rise. ✨
  • timestamp β€” TODO: NOT YET DOCUMENTED.
  • config_timestamp β€” TODO: NOT YET DOCUMENTED.
  • num_crtcs β€” TODO: NOT YET DOCUMENTED.
  • num_outputs β€” TODO: NOT YET DOCUMENTED.
  • num_modes β€” TODO: NOT YET DOCUMENTED.
  • names_len β€” TODO: NOT YET DOCUMENTED.
bestie these TODOs are in the actual manual, i'm not gatekeeping info from you, the page itself just hasn't been written yet πŸ’€

🌸 DESCRIPTION 🌸

...yeah. it's empty in the original too. we move. πŸšΆβ™€οΈπŸ’¨


πŸŽ€ RETURN VALUE πŸŽ€

Returns an xcb_randr_get_screen_resources_current_cookie_t. errors have to be handled when calling the reply function xcb_randr_get_screen_resources_current_reply.

If you want to handle errors in the event loop instead, use xcb_randr_get_screen_resources_current_unchecked. See xcb-requests(3) for details.

like, cookie first, check the errors later β€” or go unchecked and handle it in the event loop. pick your fighter. πŸ‘‘


πŸ”₯ ERRORS πŸ”₯

This request does never generate any errors.

no drama, no errors. she's low maintenance. periodt. 🧚


πŸ‘‘ SEE ALSO πŸ‘‘

(empty in the original, bestie β€” nothing to see here, literally πŸ’œ)


πŸ’œ AUTHOR πŸ’œ

Generated from randr.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.

like, if something's wrong, tell the list, don't tell me, i'm just the messenger 🫢


and that's the whole page!! brought to you by X Version 11 and libxcb 1.17.0 β€” go forth and query those screen resources, bestie, you're the main character of this X session fr fr πŸ’–βœ¨πŸŽ€πŸ¦‹πŸŒΈπŸ’