xcb_shape_notify_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_shape_notify_event_t πŸ’–

okay so bestie, welcome to the XCB Events section of the manual β€” this is xcb_shape_notify_event_t(3), and she's a whole event datastructure, no cap. sit down, grab a boba, we're doing structs today πŸ§‹βœ¨


🌸 NAME 🌸

xcb_shape_notify_event_t β€” and honestly? that's it. that's the whole name section. the original manpage left it blank after the dash so we're leaving it blank too. iconic minimalism, i guess πŸ’…


✨ SYNOPSIS ✨

first things first, you gotta pull her in:

#include <xcb/shape.h>

πŸŽ€ Event datastructure

here's the actual struct, copied character for character because we do NOT freestyle on struct definitions:

typedef struct xcb_shape_notify_event_t {
    uint8_t          response_type;
    xcb_shape_kind_t shape_kind;
    uint16_t         sequence;
    xcb_window_t     affected_window;
    int16_t          extents_x;
    int16_t          extents_y;
    uint16_t         extents_width;
    uint16_t         extents_height;
    xcb_timestamp_t  server_time;
    uint8_t          shaped;
    uint8_t          pad0[11];
} xcb_shape_notify_event_t;

look at her. eleven whole members plus a little pad0[11] for padding. she's built different 🫢


πŸ”₯ EVENT FIELDS πŸ”₯

okay so here's the field-by-field breakdown, and yes, we're doing all of them, even the ones that say NOT YET DOCUMENTED, because we don't skip content in this house 🏠

  • response_type β€” the type of this event, which in this specific case is XCB_SHAPE_NOTIFY. this same field also lives inside xcb_generic_event_t, and it's how you tell one event apart from another when they're all just vibing in the same queue. it's giving name tag at a party 🏷️
  • sequence β€” the sequence number of the last request that got processed by the X11 server. think of it as the server's "last seen" timestamp but for requests πŸ“‹
  • shape_kind β€” NOT YET DOCUMENTED. yeah. the manpage said what it said. we're not making stuff up, bestie, that's the whole rule 😭
  • affected_window β€” NOT YET DOCUMENTED.
  • extents_x β€” NOT YET DOCUMENTED.
  • extents_y β€” NOT YET DOCUMENTED.
  • extents_width β€” NOT YET DOCUMENTED.
  • extents_height β€” NOT YET DOCUMENTED.
  • server_time β€” NOT YET DOCUMENTED.
  • shaped β€” NOT YET DOCUMENTED.
ngl the original documentation really said "figure it out" for like eight of these fields. not me defending it, just reporting the facts fr fr πŸ™ˆ

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so. the description section? she's empty. there is nothing in here. the original manpage put the heading down and then simply did not elaborate. main character energy honestly β€” showing up to the function with zero explanation πŸ’€


πŸ’œ SEE ALSO πŸ’œ

also empty. no cross-references, no siblings, nothing. she's an only child and she's thriving 🌈


πŸ‘‘ AUTHOR πŸ‘‘

generated from shape.xml. if you spot something wrong and wanna send corrections or improvements, hit up xcb@lists.freedesktop.org β€” they're the ones who actually know things 🫢


and that's the whole page, bestie! this little gem came to you from X Version 11, libxcb 1.17.0, and it's filed under xcb_shape_notify_event_t(3). go forth and shape your windows, you absolute icon πŸ’…βœ¨πŸŒΈ