xcb_x_print_p...ge_resolution(3)
π
xcb_x_print_print_get_image_resolution β a lil XCB moment (from the xcb_x_print_p...ge_resolution(3) page, XCB Requests, bestie)
okay so you found yourself in the xcb_x_print_p...ge_resolution(3) manpage and honestly? slay. it's a short one, but we're gonna make it cute. this is a libxcb request page, no cap.
β¨ NAME β¨
xcb_x_print_print_get_image_resolution β and that's literally it, the NAME section left it blank like a girl who said "I'll text you back" π
πΈ SYNOPSIS πΈ
first up, the include, keep it exact:
#include <xcb/xprint.h>
π Request function
xcb_x_print_print_get_image_resolution_cookie_t
xcb_x_print_print_get_image_resolution(xcb_connection_t *conn,
xcb_x_print_pcontext_t context);
π¦ Reply datastructure
typedef struct xcb_x_print_print_get_image_resolution_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
uint16_t image_resolution;
} xcb_x_print_print_get_image_resolution_reply_t;
π Reply function
xcb_x_print_print_get_image_resolution_reply_t
*xcb_x_print_print_get_image_resolution_reply(xcb_connection_t *conn,
xcb_x_print_print_get_image_resolution_cookie_t cookie,
xcb_generic_error_t **e);
like, she's giving very "ask the server a question, get a cookie, come back later for the tea" energy. periodt.
π REQUEST ARGUMENTS π
connβ your XCB connection to X11. the whole vibe depends on her π«Άcontextβ TODO: NOT YET DOCUMENTED. yeah bestie, the docs really said "mystery" π
π REPLY FIELDS π
response_typeβ the type of this reply, which in this case isXCB_X_PRINT_PRINT_GET_IMAGE_RESOLUTION. this field is also chillin' in thexcb_generic_reply_t, so you can use it to tell replies apart from each other. very "which one of y'all texted me" πsequenceβ the sequence number of the last request processed by the X11 server. she's keeping receipts.lengthβ the length of the reply, in words (a word is 4 bytes, in case anyone was wondering, and now you know β¨).image_resolutionβ TODO: NOT YET DOCUMENTED. again. the mystery continues, i fear π
π DESCRIPTION π
nothing here. empty. a blank canvas. the DESCRIPTION section is giving "no thoughts, head empty" π
π RETURN VALUE π
Returns an xcb_x_print_print_get_image_resolution_cookie_t. errors have to be handled when you call the reply function xcb_x_print_print_get_image_resolution_reply.
If you'd rather handle errors in the event loop instead, use xcb_x_print_print_get_image_resolution_unchecked. See xcb-requests(3) for details β she explains it way better, go read her. π¦
π« ERRORS π«
This request does never generate any errors. not a single one. she's unproblematic, lowkey iconic. π
π₯ SEE ALSO π₯
the SEE ALSO section is empty. nothing to link, nothing to see, just vibes. πΈ
π«Ά AUTHOR π«Ά
Generated from xprint.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.
and that's the whole page, bestie! π this came to you from X Version 11, libxcb 1.17.0 β xcb_x_print_p...ge_resolution(3), signing off. go forth and get your image resolution, or don't, no pressure, mwah πβ¨π
π¦ 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