xcb_shm_completion_event_t(3)
β¨ xcb_shm_completion_event_t β¨
okay bestie, welcome to the xcb_shm_completion_event_t page π this is one of the XCB Events girlies, and honestly? she's giving "your shared memory upload finished, congrats queen" π
πΈ NAME πΈ
xcb_shm_completion_event_t β the event that reports your XCB_SHM_PUT_IMAGE request has completed π«Ά no cap, that's literally her whole job.
π¦ SYNOPSIS π¦
#include <xcb/shm.h>
π Event datastructure π
ok so here's the whole struct, character for character, do NOT freestyle on this:
typedef struct xcb_shm_completion_event_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
xcb_drawable_t drawable;
uint16_t minor_event;
uint8_t major_event;
uint8_t pad1;
xcb_shm_seg_t shmseg;
uint32_t offset;
} xcb_shm_completion_event_t;
π EVENT FIELDS π
every single field, explained, because we do not gatekeep here:
response_typeβ the type of this event, and in this case it'sXCB_SHM_COMPLETION. this field also lives in thexcb_generic_event_t, so you can use it to tell your events apart from each other. it's giving name tag at a party πsequenceβ the sequence number of the last request the X11 server processed. the receipts, basically π§Ύdrawableβ the drawable that got used in theXCB_SHM_PUT_IMAGErequest. main character of the image, tbh πΌοΈminor_eventβ the minor opcode used in the request. it's alwaysXCB_SHM_PUT_IMAGE, every single time, no exceptions β¨major_eventβ the major opcode used in the request. it's always the opcode of the MIT-SHM extension. periodt πshmsegβ the shared memory segment that got used in the request πoffsetβ the offset in that shared memory segment that got used in the request. yes, the little positional detail, we love her π
π DESCRIPTION π
the X server generates this one to report that an XCB_SHM_PUT_IMAGE request has been successfully processed. that's it, that's the tea β a lil confirmation notification, from the server to you, because she's thoughtful like that π
β SEE ALSO β
xcb_generic_event_t(3)
π«Ά AUTHOR π«Ά
generated from shm.xml. if you wanna send corrections and improvements, hit up xcb@lists.freedesktop.org β they're literally so responsive, iykyk π
ok that's the whole page bestie, slay π this was served to you from X Version 11, libxcb 1.17.0 β stan a stable library release, mwah ππ
π¦ where this page comes from
- alpine 3.22: libxcb-doc 1.17.0-r0 Β· MIT
- alpine 3.23: libxcb-doc 1.17.0-r1 Β· MIT
- alpine 3.24: libxcb-doc 1.17.0-r2 Β· MIT
- arch rolling: libxcb 1.17.0-1 Β· X11
- centos-stream 10: libxcb-devel 1.17.0-3.el10 Β· X11
- debian trixie: libxcb-doc 1.17.0-2
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- nixpkgs unstable: libxcb 1.17.0
- opensuse-leap 16.0: libxcb-devel-doc 1.17.0-160000.2.2 Β· MIT
- ubuntu questing: libxcb-doc 1.17.0-2build1
- ubuntu resolute: libxcb-doc 1.17.0-2ubuntu1
- ubuntu stonking: libxcb-doc 1.17.0-2ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms