xcb_dri2_wait_msc(3)

✨ NAME ✨

xcb_dri2_wait_msc — okay so bestie, this one is a mystery 💀 the original page literally just gives us the name and a lonely little dash, no description at all. So like… it's the xcb_dri2_wait_msc request from the DRI2 crew, and that's genuinely all the manpage tells us. Iconic minimalism, I guess? 🎀

---

🌸 SYNOPSIS 🌸

First things first, you gotta pull in the header:

#include <xcb/dri2.h>

💅 Request function

xcb_dri2_wait_msc_cookie_t xcb_dri2_wait_msc(xcb_connection_t *conn,
       xcb_drawable_t drawable, uint32_t target_msc_hi,
       uint32_t target_msc_lo, uint32_t divisor_hi, uint32_t divisor_lo,
       uint32_t remainder_hi, uint32_t remainder_lo);

🦋 Reply datastructure

This is the little struct you get back, and yes, every field is exactly where it should be:

typedef struct xcb_dri2_wait_msc_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint32_t ust_hi;
    uint32_t ust_lo;
    uint32_t msc_hi;
    uint32_t msc_lo;
    uint32_t sbc_hi;
    uint32_t sbc_lo;
} xcb_dri2_wait_msc_reply_t;

⭐ Reply function

xcb_dri2_wait_msc_reply_t
       *xcb_dri2_wait_msc_reply(xcb_connection_t *conn,
       xcb_dri2_wait_msc_cookie_t cookie, xcb_generic_error_t **e);

---

🎀 REQUEST ARGUMENTS 🎀

• conn — your XCB connection to X11. The whole vibe starts here, bestie 🫶
• drawable — TODO: NOT YET DOCUMENTED. (The docs really said "figure it out" 😭)
• target_msc_hi — TODO: NOT YET DOCUMENTED.
• target_msc_lo — TODO: NOT YET DOCUMENTED.
• divisor_hi — TODO: NOT YET DOCUMENTED.
• divisor_lo — TODO: NOT YET DOCUMENTED.
• remainder_hi — TODO: NOT YET DOCUMENTED.
• remainder_lo — TODO: NOT YET DOCUMENTED.

Not me having to relay "TODO: NOT YET DOCUMENTED" eight whole times 💀 that's on the original authors, not me, I'm just the messenger 🧚

---

🌈 REPLY FIELDS 🌈

• response_type — the type of this reply, which in this case is XCB_DRI2_WAIT_MSC. It also lives in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other. Slay, a field with a job 💅
• sequence — the sequence number of the last request the X11 server processed. It's giving "receipts" 🔥
• length — how long the reply is, in words (and a word is 4 bytes, so do the math bestie).
• ust_hi — TODO: NOT YET DOCUMENTED.
• ust_lo — TODO: NOT YET DOCUMENTED.
• msc_hi — TODO: NOT YET DOCUMENTED.
• msc_lo — TODO: NOT YET DOCUMENTED.
• sbc_hi — TODO: NOT YET DOCUMENTED.
• sbc_lo — TODO: NOT YET DOCUMENTED.

---

💜 DESCRIPTION 💜

Okay so… there is nothing here. The original page has the DESCRIPTION heading and then absolutely zero words underneath it. An empty section. A void. The silence is loud 😭🙈

---

✨ RETURN VALUE ✨

It hands you back an xcb_dri2_wait_msc_cookie_t. The catch? Errors have to be handled when you call the reply function xcb_dri2_wait_msc_reply.

And if you'd rather handle errors in the event loop instead, use xcb_dri2_wait_msc_unchecked. Peep xcb-requests(3) for all the deets 👑

---

💀 ERRORS 💀

Good news, no cap: this request does never generate any errors. Zero. None. A flawless queen 👑

---

🦋 SEE ALSO 🦋

Nothing listed here, bestie. The original page left this section empty too. We move in silence 🎀

---

🌸 AUTHOR 🌸

Generated from dri2.xml. If you wanna send corrections and improvements, hit up xcb@lists.freedesktop.org — they're taking notes, fr fr 🫶

---

And that's a wrap on the xcb_dri2_wait_msc(3) page, bestie! 💖 This one comes to you from the X Version 11 era, libxcb 1.17.0 edition, and yeah — a whole lot of it is genuinely still "TODO: NOT YET DOCUMENTED," which is lowkey tragic but also kind of a mood. Go forth and slay your DRI2 waiting, mwah 💅✨