xcb_dpms_info(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_dpms_info ✨

okay bestie, welcome to the xcb_dpms_info page from the XCB Requests corner of the libxcb universe 🫢 it's a lil one, but it's ours.


🌸 NAME 🌸

xcb_dpms_info -

(yes the description is literally just a dash, no cap, the manpage is giving mysterious πŸ’€ we move.)


πŸŽ€ SYNOPSIS πŸŽ€

#include <xcb/dpms.h>

πŸ’… Request function

xcb_dpms_info_cookie_t xcb_dpms_info(xcb_connection_t *conn,

πŸ¦‹ Reply datastructure

typedef struct xcb_dpms_info_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint16_t power_level;
    uint8_t  state;
    uint8_t  pad1[21];
} xcb_dpms_info_reply_t;

⭐ Reply function

xcb_dpms_info_reply_t *xcb_dpms_info_reply(xcb_connection_t *conn,
       xcb_dpms_info_cookie_t cookie, xcb_generic_error_t **e);

πŸ’– REQUEST ARGUMENTS πŸ’–

  • conn β€” your XCB connection to X11. that's the whole list, she's low maintenance πŸ‘‘

🌈 REPLY FIELDS 🌈

  • response_type β€” the type of this reply, and in this case it's XCB_DPMS_INFO. it also lives in the xcb_generic_reply_t, so you can use it to tell replies apart from each other. very "which one of you is this" energy πŸ”
  • sequence β€” the sequence number of the last request processed by the X11 server. it's giving receipt 🧾
  • length β€” the length of the reply, in words. and reminder bestie, a word is 4 bytes ✨
  • power_level β€” TODO: NOT YET DOCUMENTED. πŸ’€
  • state β€” TODO: NOT YET DOCUMENTED. πŸ’€

πŸŽ€ DESCRIPTION πŸŽ€

...yeah. it's empty. the DESCRIPTION section is out here living its best silent main character life πŸ™ˆ no notes, no lore, nothing. iconic of it honestly.


🫢 RETURN VALUE 🫢

It returns an xcb_dpms_info_cookie_t. Errors have to be handled when calling the reply function xcb_dpms_info_reply.

If you want to handle errors in the event loop instead, use xcb_dpms_info_unchecked. See xcb-requests(3) for details.


πŸ’€ ERRORS πŸ’€

This request does never generate any errors.

seriously, zero. not a single one. she's flawless, no cap ✨

πŸ”₯ SEE ALSO πŸ”₯

(nothing listed here β€” the original is a ghost town too πŸ‘»)


πŸ‘‘ AUTHOR πŸ‘‘

Generated from dpms.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.


and that's the whole page bestie!! 🌸 this one came from X Version 11, specifically libxcb 1.17.0, and it's tagged as xcb_dpms_info(3) β€” go forth and query that DPMS info, you absolute legend πŸ’…πŸŽ€πŸ¦‹