XCB_X_PRINT_PRINT_QUERY_SCREENS_UNCHECKED(3)

✨ xcb_x_print_print_query_screens — the XCB Requests era 💅

okay bestie, gather round 🫶 this is the manual page for xcb_x_print_print_query_screens(3), living happily inside the XCB Requests section of your friendly neighbourhood libxcb docs. No cap, it's a whole little X Print request and we're gonna walk it together like it's a group chat. 🌸

---

🌈 NAME 🌈

xcb_x_print_print_query_screens —

so like... the description is literally empty in the original. Iconic of them honestly. We move. 💀

---

🎀 SYNOPSIS 🎀

First things first, you gotta pull in the header:

#include <xcb/xprint.h>

✨ Request function ✨

xcb_x_print_print_query_screens_cookie_t
       xcb_x_print_print_query_screens(xcb_connection_t *conn,

(yes the original cuts off right there after that trailing comma, we do not edit the source material, we respect the source material 💖)

🦋 Reply datastructure 🦋

typedef struct xcb_x_print_print_query_screens_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint32_t listCount;
    uint8_t  pad1[20];
} xcb_x_print_print_query_screens_reply_t;

look at those lil padding arrays, they're just vibing 🌈

💜 Reply function 💜

xcb_x_print_print_query_screens_reply_t
       *xcb_x_print_print_query_screens_reply(xcb_connection_t *conn,
       xcb_x_print_print_query_screens_cookie_t cookie,
       xcb_generic_error_t **e);

⭐ Reply accessors ⭐

xcb_window_t *xcb_x_print_print_query_screens_roots(const
       xcb_x_print_print_query_screens_request_t *reply);

int xcb_x_print_print_query_screens_roots_length(const
       xcb_x_print_print_query_screens_reply_t *reply);

xcb_generic_iterator_t xcb_x_print_print_query_screens_roots_end(const
       xcb_x_print_print_query_screens_reply_t *reply);

---

🔥 REQUEST ARGUMENTS 🔥

• conn — bestie this is literally just your XCB connection to X11. the whole entire link to the server. the main character of the argument list, honestly 👑

---

🌸 REPLY FIELDS 🌸

• response_type — the type of this reply, and for this one specifically it's XCB_X_PRINT_PRINT_QUERY_SCREENS. This field also lives inside xcb_generic_reply_t, so you can use it to tell replies apart from each other. like name tags at a party 🎀
• sequence — the sequence number of the last request that got processed by the X11 server. it's giving "what order are we in" energy ⭐
• length — the length of the reply, measured in words. and before you ask, a word is 4 bytes. periodt. 💅
• listCount — TODO: NOT YET DOCUMENTED. yeah they just left this one blank bestie, it's an unsolved mystery, we don't make stuff up here 🙈

---

💖 DESCRIPTION 💖

...it's empty. genuinely nothing. the void. the silence. we respect it 🫶

---

✨ RETURN VALUE ✨

You get back an xcb_x_print_print_query_screens_cookie_t. 🍪 Errors have to be handled when you call the reply function, xcb_x_print_print_query_screens_reply.

If you'd rather handle your errors in the event loop instead (valid, honestly), use xcb_x_print_print_query_screens_unchecked. Peep xcb-requests(3) for the details on all that.

---

💀 ERRORS 💀

This request does never generate any errors.

not a single one. zero. no drama. we love a low-maintenance request. 🧚

---

🌈 SEE ALSO 🌈

...also empty. they said "you already know" and honestly, iykyk 💜

---

👑 AUTHOR 👑

Generated from xprint.xml. If you've got corrections or improvements, hit up xcb@lists.freedesktop.org — they're literally asking for your feedback, so slide into those emails bestie 🫶

---

and that's the whole page! footer tea for you: this is X Version 11, libxcb 1.17.0 🌸 stay hydrated, handle your errors when you call the reply function, and don't forget the padding arrays. mwah 💅✨