xcb_x_print_a...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

πŸ’– NAME πŸ’–

xcb_x_print_attribut_notify_event_t β€” bestie, it's a whole event datastructure, and it's giving "X Print" energy fr fr πŸ–¨οΈβœ¨


🌸 SYNOPSIS 🌸

#include <xcb/xprint.h>

πŸŽ€ Event datastructure πŸŽ€

typedef struct xcb_x_print_attribut_notify_event_t {
    uint8_t                response_type;
    uint8_t                detail;
    uint16_t               sequence;
    xcb_x_print_pcontext_t context;
} xcb_x_print_attribut_notify_event_t;

Like. That's the whole struct. Four fields. It's minimal, it's clean, it's lowkey iconic πŸ’…


✨ EVENT FIELDS ✨

  • response_type β€” the type of this event, and in this case it's XCB_X_PRINT_ATTRIBUT_NOTIFY. This same field also lives inside xcb_generic_event_t, so you can use it to tell your events apart from each other. It's literally the vibe check of the event world πŸ¦‹
  • sequence β€” the sequence number of the last request that got processed by the X11 server. So like, "where were we in the timeline" energy ⏳
  • detail β€” NOT YET DOCUMENTED. Yeah. Nobody wrote it. It's a mystery, bestie πŸ˜­πŸ™ˆ
  • context β€” also NOT YET DOCUMENTED. Also a mystery. Two mysteries. We move 🫢

🌈 DESCRIPTION 🌈

Nothing here yet! The original page is silent on this one, so we're not gonna make stuff up. No cap, if there's no description, there's no description. Periodt πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

Empty, bestie. There are no SEE ALSO references on this page. It's just out here solo, main character energy, no entourage ✨

πŸ’œ AUTHOR πŸ’œ

Generated from xprint.xml. If you spot something wrong and wanna fix it or suggest improvements, hit up xcb@lists.freedesktop.org β€” they're the ones to contact πŸ“§πŸ’–


And that's the whole page, babes! This beauty came from X Version 11, libxcb 1.17.0 β€” go forth and print, and remember: the detail and context fields are undocumented, so if you figure them out, that's between you and the source code πŸ’…πŸŽ€πŸ¦‹