xcb_xinerama_get_state(3)

💅 xcb_xinerama_get_state — bestie edition

okay so real talk: this is xcb_xinerama_get_state(3), part of the XCB Requests lineup, and it lives in libxcb. It's a little request that asks the X server "hey, what's the Xinerama state looking like rn?" and hands you back a cookie so you can go get the answer later. Let's get into it 🫶

---

✨ SYNOPSIS ✨

First things first, you gotta include the header:

#include <xcb/xinerama.h>

🎀 Request function

xcb_xinerama_get_state_cookie_t
       xcb_xinerama_get_state(xcb_connection_t *conn,
       xcb_window_t window);

🦋 Reply datastructure

typedef struct xcb_xinerama_get_state_reply_t {
    uint8_t      response_type;
    uint8_t      state;
    uint16_t     sequence;
    uint32_t     length;
    xcb_window_t window;
} xcb_xinerama_get_state_reply_t;

🌸 Reply function

xcb_xinerama_get_state_reply_t
       *xcb_xinerama_get_state_reply(xcb_connection_t *conn,
       xcb_xinerama_get_state_cookie_t cookie, xcb_generic_error_t **e);

---

💖 REQUEST ARGUMENTS 💖

• conn — the XCB connection to X11. your lil hotline to the server, no cap ☎️
• window — TODO: NOT YET DOCUMENTED. yeah bestie, the docs really just left us on read here 😭

---

👑 REPLY FIELDS 👑

• response_type — the type of this reply, which in this case is XCB_XINERAMA_GET_STATE. it also shows up in the xcb_generic_reply_t, so you can use it to tell replies apart from each other. it's giving name tag at a party 🏷️
• sequence — the sequence number of the last request processed by the X11 server. lowkey your receipt number for "what order did stuff happen in" 🧾
• length — the length of the reply, in words (and a word is 4 bytes, periodt).
• state — TODO: NOT YET DOCUMENTED. the mystery field 🙈
• window — TODO: NOT YET DOCUMENTED. also a mystery, also not my fault, blame the XML 💀

---

🌈 DESCRIPTION 🌈

...yeah there's literally nothing here. the original page said nothing and I'm not about to invent lore, bestie. moving on with our lives 💅

---

⭐ RETURN VALUE ⭐

You get back an xcb_xinerama_get_state_cookie_t 🍪 — iconic, delicious, but not the actual answer yet. Errors have to be handled when you call the reply function xcb_xinerama_get_state_reply.

If you'd rather handle errors in the event loop instead, use xcb_xinerama_get_state_unchecked. See xcb-requests(3) for the deets. iykyk 🔥

---

💀 ERRORS 💀

This request does never generate any errors. not one. zero. it's the chillest request at the function sleepover 😌

---

🦄 SEE ALSO 🦄

(empty, bestie — nothing to link, the page just left this section vibing on its own 🌸)

---

💜 AUTHOR 💜

Generated from xinerama.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. like, fr fr, they wanna hear from you 🫶

---

and that's the whole page, bestie ✨ this came to you from X Version 11, libxcb 1.17.0, and the page is xcb_xinerama_get_state(3). stay hydrated, read your manpages, and slay 💖🎀🦋