xcb_dpms_info_notify_event_t(3)

📦
version 1.17.0 · 2 versions
  • 1.17.0 · 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 (latest)
  • 1.15 · ubuntu noble
, 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_notify_event_t — the XCB Events girlies know 💖

okay so bestie, this one lives in the XCB Events section of the manual (that's the <cyan>3</cyan> up in the corner, iykyk). It's a struct page, it's giving very "here is a datastructure, go forth and slay", and honestly? It eats. Let's get into it. 🦋

✨ NAME ✨

xcb_dpms_info_notify_event_t — (the description slot is literally empty, no cap, the original just trails off with a dash and honestly? relatable. it's giving mysterious main character energy 💅)

✨ SYNOPSIS ✨

First things first, you gotta pull in the header:

#include <xcb/dpms.h>

🎀 Event datastructure

Here's the whole vibe, field by field, exactly as it is:

typedef struct xcb_dpms_info_notify_event_t {
    uint8_t         response_type;
    uint8_t         extension;
    uint16_t        sequence;
    uint32_t        length;
    uint16_t        event_type;
    uint8_t         pad0[2];
    xcb_timestamp_t timestamp;
    uint16_t        power_level;
    uint8_t         state;
    uint8_t         pad1[21];
} xcb_dpms_info_notify_event_t;

not the pad0[2] and pad1[21] doing their little structural support thing, iconic behavior honestly 🌸

✨ EVENT FIELDS ✨

  • response_type — this is the type of the event, and in this case it's XCB_DPMS_INFO_NOTIFY. plot twist: this field ALSO shows up in the xcb_generic_event_t, so you can use it to tell your events apart from each other. Very "which one of y'all is it" energy. 🔥
  • sequence — the sequence number of the last request that got processed by the X11 server. bestie's receipt number, basically. 🧾
  • extension — NOT YET DOCUMENTED. (mystery. we don't know her yet 🙈)
  • length — NOT YET DOCUMENTED. (also a mystery ✨)
  • event_type — NOT YET DOCUMENTED. (the mystery continues 😭)
  • timestamp — NOT YET DOCUMENTED. (girl where are the docs 💀)
  • power_level — NOT YET DOCUMENTED. (okay but is this a power level like anime or a power level like battery, the docs simply will not say 🌈)
  • state — NOT YET DOCUMENTED. (screaming, crying, undocumented 🫶)

✨ DESCRIPTION ✨

(nothing here. the section exists, it's just vibing. we respect that.)

✨ SEE ALSO ✨

(also empty! the "see also" section saw nothing and also'd nothing. truly minimalist of it.)

✨ AUTHOR ✨

Generated from dpms.xml. If you spot something wrong or wanna slide in with improvements, hmu at xcb@lists.freedesktop.org. They're accepting corrections, so don't be shy 🫶

⭐ heads up: a bunch of these fields are marked NOT YET DOCUMENTED and I am NOT out here inventing lore for them. That's the actual state of the page, periodt.

and that's the whole page, bestie! 💖 This one came from the XCB Events corner of X Version 11, living in libxcb 1.17.0 — go forth, tell your events apart by their response_type, and stay hydrated. 🦋✨🌸

📦 where this page comes from