xcb_client_message_event_t(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_client_message_event_t(3) 💖

okay bestie, welcome to the XCB Events corner of the manual, page xcb_client_message_event_t(3). buckle up, this one's a struct and she's got ✨lore✨.

🌸 NAME 🌸

xcb_client_message_event_t — NOT YET DOCUMENTED</p> 🙈

yes fr fr, that's genuinely what the manual says. iconic of them honestly. but don't worry, i got you — everything the page does say is right below, no cap.

🎀 SYNOPSIS 🎀

#include <xcb/xproto.h>

🦋 Event datastructure 🦋

typedef struct xcb_client_message_event_t {
    uint8_t                   response_type;
    uint8_t                   format;
    uint16_t                  sequence;
    xcb_window_t              window;
    xcb_atom_t                type;
    xcb_client_message_data_t data;
} xcb_client_message_event_t;

look at her. six fields. main character energy 💅

✨ EVENT FIELDS ✨

  • response_type — the type of this event, and in this specific case it's XCB_CLIENT_MESSAGE. this field also lives in the xcb_generic_event_t, and that's literally the whole point: it's how you tell events apart from each other. vibe check your events with it 🔥
  • sequence — the sequence number of the last request processed by the X11 server. yes bestie, the last request processed. that's what it says 🫶
  • format — tells you how to interpret data. it can be either 8, 16 or 32. that's it, those are the options, no in-between 🌈
  • window — NOT YET DOCUMENTED.</p> 😭 (again. i know. i'm sorry. it's not me, it's the manpage.)
  • type — an atom that indicates how the data should be interpreted by the receiving client. it's giving "here's a hint for whoever's on the other end" 💌
  • data — the data itself. max 20 bytes. that's the whole budget, bestie, spend it wisely 🍓

💜 DESCRIPTION 💜

so this event represents a ClientMessage, sent by another X11 client. that's the whole plot.

an example, and it's a good one: a client sending the _NET_WM_STATE ClientMessage to the root window to indicate the fullscreen window state — which effectively requests that the window manager puts it into fullscreen mode. like, "hey wm, bestie, make this fullscreen please" and the wm is supposed to hear you 👑

🌟 SEE ALSO 🌟

💌 AUTHOR 💌

Generated from xproto.xml. if you want corrections or improvements, contact xcb@lists.freedesktop.org. they're literally asking for the feedback, so go off 🎀

and that's the page, babes 💖 this manual page ships as part of X Version 11, libxcb 1.17.0 — thanks for reading the whole thing, you ate that fr fr. now go handle some ClientMessages, mwah 💅✨

📦 where this page comes from