xcb_x_print_p...ge_resolution(3)

πŸ“¦
version 1.17.0 Β· 4 versions
, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, centos-stream 10, debian trixie, fedora 43, fedora 44, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’… 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 is XCB_X_PRINT_PRINT_GET_IMAGE_RESOLUTION. this field is also chillin' in the xcb_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 πŸŽ€βœ¨πŸ’