xcb_configure_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_configure_notify_event_t πŸ’–

okay so bestie, welcome to the xcb_configure_notify_event_t(3) page β€” it lives in the XCB Events section of the manual and it's genuinely the moment your window got reconfigured. new size, new spot, new border, new stacking, the whole glow-up. no cap.


✨ NAME ✨

xcb_configure_notify_event_t β€” NOT YET DOCUMENTED 😭 (yes fr, that's literally what it says, the upstream page is giving mystery)


✨ SYNOPSIS ✨

#include <xcb/xproto.h>

πŸŽ€ Event datastructure πŸŽ€

typedef struct xcb_configure_notify_event_t {
    uint8_t      response_type;
    uint8_t      pad0;
    uint16_t     sequence;
    xcb_window_t event;
    xcb_window_t window;
    xcb_window_t above_sibling;
    int16_t      x;
    int16_t      y;
    uint16_t     width;
    uint16_t     height;
    uint16_t     border_width;
    uint8_t      override_redirect;
    uint8_t      pad1;
} xcb_configure_notify_event_t;

look at that struct. she's iconic. every field matters, so let's go field by field πŸ’…


🌸 EVENT FIELDS 🌸

  • response_type β€” the type of this event, and in this case it's XCB_CONFIGURE_NOTIFY. this field is also chillin' inside xcb_generic_event_t, so you can use it to tell your events apart from each other. it's the little name tag at the party πŸŽ€
  • sequence β€” the sequence number of the last request processed by the X11 server. like the receipt number of the last thing the server handled 🧾
  • event β€” the reconfigured window or its parent, depending on whether StructureNotify or SubstructureNotify was selected. so who's the one reporting the tea? depends on your selection, bestie ✨
  • window β€” the actual window whose size, position, border, and/or stacking order was changed. main character energy right here πŸ‘‘
  • above_sibling β€” if it's XCB_NONE, the window is on the bottom of the stack with respect to sibling windows. but if it's set to a sibling window, the window is placed on top of this sibling window. so either she's at the bottom of the pile or she's standing on somebody's shoulders πŸ’€
  • x β€” the X coordinate of the upper-left outside corner of window, relative to the parent window's origin πŸ“
  • y β€” the Y coordinate of the upper-left outside corner of window, relative to the parent window's origin πŸ“
  • width β€” the inside width of window, not including the border. inside measurements only, we don't count the fit πŸ“
  • height β€” the inside height of window, not including the border. same deal, border not invited πŸ“
  • border_width β€” the border width of window. there it is, the fit ✨
  • override_redirect β€” window managers should ignore this window if override_redirect is 1. like, do not perceive her. she's off the grid πŸ™ˆ

πŸ’œ DESCRIPTION πŸ’œ

crickets πŸ¦—βœ¨

fr fr, there is genuinely nothing here. the original page has an empty DESCRIPTION section. not me leaving it blank too β€” the facts are the facts, bestie. no invented lore, periodt.


πŸ¦‹ SEE ALSO πŸ¦‹

go read those too, they're in the same friend group 🫢


⭐ AUTHOR ⭐

generated from xproto.xml. contact xcb@lists.freedesktop.org for corrections and improvements β€” yes, actual humans read that inbox, so if something's wrong, tell them nicely πŸ’–


and that's the whole page, bestie!! every field, every type, every constant, untouched and exactly as the source gave it. slay πŸ’…

this was X Version 11, libxcb 1.17.0, and the page is xcb_configure_notify_event_t(3) β€” catch you in the next one, mwah 😘🌈