xcb_sync_alarm_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 ✨

so this whole page is about xcb_sync_alarm_notify_event_t, which is a struct type from the XCB events gang πŸ’– and ngl the actual name line is just the struct name, a lil dash -, and nothing else. no one-line summary. no vibes described. just xcb_sync_alarm_notify_event_t - and then it moves on. iconic minimalism honestly πŸŽ€

we're in the XCB Events manual section, bestie, so you already know it's struct o'clock.


πŸ’… SYNOPSIS πŸ’…

#include <xcb/sync.h>

πŸŽ€ Event datastructure

typedef struct xcb_sync_alarm_notify_event_t {
    uint8_t          response_type;
    uint8_t          kind;
    uint16_t         sequence;
    xcb_sync_alarm_t alarm;
    xcb_sync_int64_t counter_value;
    xcb_sync_int64_t alarm_value;
    xcb_timestamp_t  timestamp;
    uint8_t          state;
    uint8_t          pad0[3];
} xcb_sync_alarm_notify_event_t;

like. look at her. the padding at the end? the little pad0[3]?? she's aligned and she knows it πŸ’…βœ¨


🌸 EVENT FIELDS 🌸

okay bestie here's the field-by-field rundown, no skipping, we go through all of them 🫢

  • response_type β€” this is the event's type tag, and for this one it's XCB_SYNC_ALARM_NOTIFY. it also shows up in the 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 the X11 server processed. your lil receipt number fr fr 🧾
  • kind β€” NOT YET DOCUMENTED. yeah. it's giving mystery. 😭
  • alarm β€” NOT YET DOCUMENTED. also a mystery, we simply do not know 🫠
  • counter_value β€” NOT YET DOCUMENTED. no thoughts, head empty 🌸
  • alarm_value β€” NOT YET DOCUMENTED. same energy πŸ™ˆ
  • timestamp β€” NOT YET DOCUMENTED. time is fake anyway ⏰
  • state β€” NOT YET DOCUMENTED. the state of what? unknown. the state of the union? unclear. πŸ’€
real talk: a whole bunch of these fields are literally documented as NOT YET DOCUMENTED in the source. i'm not gonna invent lore for them, because that would be lying to you and you deserve better. when the docs say nothing, i say nothing. periodt.

πŸ¦‹ DESCRIPTION πŸ¦‹

bestie. there is no description. the section exists and then immediately does not. it's an empty room with the lights on πŸ’‘πŸšͺ

(no cap, the original page has the heading and zero content under it. we respect the silence. 🧘)


πŸ‘‘ SEE ALSO πŸ‘‘

nothing here either. no cross-references, no friends listed, no "go read this next". she's a standalone queen fr fr πŸ‘‘


πŸ’– AUTHOR πŸ’–

Generated from sync.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.

so if you spot something wrong, that's the email, and they want to hear from you β€” corrections and improvements, both welcome 🫢✨


and that's the whole page, babes πŸ’œ this came to you from X Version 11, libxcb 1.17.0, and it's filed under the XCB Events manual. stay aligned, stay padded, and go read your structs responsibly πŸŽ€πŸ¦‹πŸ’