xcb_randr_get...urces_current(3)
π 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 caseXCB_RANDR_GET_SCREEN_RESOURCES_CURRENT. this field is also present in thexcb_generic_reply_tand 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 πβ¨ππ¦πΈπ
π¦ where this page comes from
- alpine 3.22: libxcb-doc 1.17.0-r0 Β· MIT
- alpine 3.23: libxcb-doc 1.17.0-r1 Β· MIT
- alpine 3.24: libxcb-doc 1.17.0-r2 Β· MIT
- arch rolling: libxcb 1.17.0-1 Β· X11
- centos-stream 10: libxcb-devel 1.17.0-3.el10 Β· X11
- debian trixie: libxcb-doc 1.17.0-2
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- nixpkgs unstable: libxcb 1.17.0
- opensuse-leap 16.0: libxcb-devel-doc 1.17.0-160000.2.2 Β· MIT
- ubuntu questing: libxcb-doc 1.17.0-2build1
- ubuntu resolute: libxcb-doc 1.17.0-2ubuntu1
- ubuntu stonking: libxcb-doc 1.17.0-2ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms