xcb_x_print_p...ge_resolution(3)

💖 xcb_x_print_print_set_image_resolution 💖

okay bestie, welcome to the XCB corner of the X11 universe 🦋 this one lives in the XCB Requests manual, and it's literally called xcb_x_print_p...ge_resolution(3) because the title got cut off mid-glow-up (the full name is waaaay too long for the header, iykyk). It's a request function, it comes from <xcb/xprint.h>, and yes it's part of the X Print squad. Let's get into it ✨

---

🌸 NAME 🌸

xcb_x_print_print_set_image_resolution — and that's it, that's the whole name, no description. Not me being mysterious, the page genuinely just says that 💅

---

✨ SYNOPSIS ✨

First, the include, because nothing works without it:

#include <xcb/xprint.h>

🎀 Request function

xcb_x_print_print_set_image_resolution_cookie_t
       xcb_x_print_print_set_image_resolution(xcb_connection_t *conn,
       xcb_x_print_pcontext_t context, uint16_t image_resolution);

🎀 Reply datastructure

typedef struct xcb_x_print_print_set_image_resolution_reply_t {
    uint8_t  response_type;
    uint8_t  status;
    uint16_t sequence;
    uint32_t length;
    uint16_t previous_resolutions;
} xcb_x_print_print_set_image_resolution_reply_t;

🎀 Reply function

xcb_x_print_print_set_image_resolution_reply_t
       *xcb_x_print_print_set_image_resolution_reply(xcb_connection_t *conn,
       xcb_x_print_print_set_image_resolution_cookie_t cookie,
       xcb_generic_error_t **e);

---

🌈 REQUEST ARGUMENTS 🌈

• conn — the XCB connection to X11, aka your little phone line to the server 🫶
• context — TODO: NOT YET DOCUMENTED. yeah bestie, the docs just left us on read 🙈
• image_resolution — TODO: NOT YET DOCUMENTED. also left on read, no cap 😭

---

👑 REPLY FIELDS 👑

• response_type — the type of this reply, and in this specific case it's XCB_X_PRINT_PRINT_SET_IMAGE_RESOLUTION. this field is also chillin' in the xcb_generic_reply_t, which is how you tell replies apart from each other. very main character of it 💅
• sequence — the sequence number of the last request processed by the X11 server. it's giving receipt energy 🧾
• length — how long the reply is, in words (and a word is 4 bytes, so do the math ✨)
• status — TODO: NOT YET DOCUMENTED. 🙈
• previous_resolutions — TODO: NOT YET DOCUMENTED. 🙈

---

💜 DESCRIPTION 💜

literally nothing here. the section exists, it's just empty. the void. the silence. we respect it though 🌸

---

🦋 RETURN VALUE 🦋

It returns an xcb_x_print_print_set_image_resolution_cookie_t. 🍪

Errors? You have to handle those when you call the reply function, xcb_x_print_print_set_image_resolution_reply.

If you'd rather handle errors in the event loop instead, use xcb_x_print_print_set_image_resolution_unchecked. See xcb-requests(3) for the details, bestie 💖

---

🔥 ERRORS 🔥

This request does never generate any errors. zero. zilch. not a single one. iconic behaviour honestly 👑

---

⭐ SEE ALSO ⭐

(blank. empty. the page said nothing here. we're just vibing in the silence 🦋)

---

🧚 AUTHOR 🧚

Generated from xprint.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. so if something's off, slide into their inbox, not mine 💌

---

fr fr, that's the whole page. the TODOs are the original author's, not mine — I'm just the messenger 🫶

---

and that's a wrap, bestie!! 💖 This lil gem came to you from X Version 11, libxcb 1.17.0, page xcb_x_print_p...ge_resolution(3). go forth and print, you absolute legend ✨🎀🦋