xcb_xinerama_query_screens(3)
π xcb_xinerama_query_screens β bestie edition π
okay so this is a page from XCB Requests, and it's literally all about xcb_xinerama_query_screens(3). yes the NAME section is empty, don't come for me, that's just how it is π
β¨ SYNOPSIS β¨
first things first, you gotta pull in the header:
#include <xcb/xinerama.h>
π Request function
xcb_xinerama_query_screens_cookie_t
xcb_xinerama_query_screens(xcb_connection_t *conn,
π¦ Reply datastructure
typedef struct xcb_xinerama_query_screens_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
uint32_t number;
uint8_t pad1[20];
} xcb_xinerama_query_screens_reply_t;
πΈ Reply function
xcb_xinerama_query_screens_reply_t
*xcb_xinerama_query_screens_reply(xcb_connection_t *conn,
xcb_xinerama_query_screens_cookie_t cookie,
xcb_generic_error_t **e);
π Reply accessors
xcb_xinerama_screen_info_t *xcb_xinerama_query_screens_screen_info(const
xcb_xinerama_query_screens_request_t *reply);
int xcb_xinerama_query_screens_screen_info_length(const
xcb_xinerama_query_screens_reply_t *reply);
xcb_xinerama_screen_info_iterator_t
xcb_xinerama_query_screens_screen_info_iterator(const
xcb_xinerama_query_screens_reply_t *reply);
π REQUEST ARGUMENTS π
connβ the XCB connection to X11. that's it, that's the whole argument list, she's low maintenance π
β REPLY FIELDS β
response_typeβ the type of this reply, which in this case isXCB_XINERAMA_QUERY_SCREENS. this field also lives in thexcb_generic_reply_t, so you can use it to tell your replies apart from each other. very much "which one of y'all is this" energy πsequenceβ the sequence number of the last request the X11 server actually processed. the receipts, basically π§Ύlengthβ the length of the reply, measured in words. and bestie, a word is 4 bytes. write that down πnumberβTODO: NOT YET DOCUMENTED.yeah. nobody wrote it. it's giving mystery, it's giving main character with no backstory π
π DESCRIPTION π
nothing here. genuinely empty. the description said "not today" and left π«Ά
π₯ RETURN VALUE π₯
so it hands you back an xcb_xinerama_query_screens_cookie_t. the errors? you don't deal with them here, you have to handle them when you call the reply function xcb_xinerama_query_screens_reply.
and if you'd rather catch errors in the event loop instead? use xcb_xinerama_query_screens_unchecked. peek xcb-requests(3) for the whole tea β
π« ERRORS π«
This request does never generate any errors. not a single one. flawless behaviour, no notes, she ate and left no crumbs β¨
π SEE ALSO π
(empty, bestie. nothing to see. the see also said see nothing π)
π«Ά AUTHOR π«Ά
Generated from xinerama.xml. if you spot something wrong and want corrections and improvements, hit up xcb@lists.freedesktop.org β they're literally waiting for your email π
and that's the whole page!! this came from X Version 11, libxcb 1.17.0, and it's the xcb_xinerama_query_screens(3) page β go forth and query those screens, you absolute icon πβ¨π¦
π¦ 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