xcb_poly_point(3)

💅 xcb_poly_point

okay bestie, welcome to the xcb_poly_point(3) page — it lives in the XCB Requests corner of the libxcb universe, and it's giving "draw a whole bunch of points in one go" energy. she's short, she's sweet, and half her docs are literally just the word TODO, so let's vibe through her together 🎀

---

✨ NAME ✨

xcb_poly_point — the request itself. that's it, that's the name, no little dash-summary for us today, we ball 🙈

---

🌸 SYNOPSIS 🌸

first things first, you gotta pull in the header:

#include <xcb/xproto.h>

🦋 Request function

here's the whole squad, exactly as they show up:

xcb_void_cookie_t xcb_poly_point(xcb_connection_t *conn,
       uint8_t coordinate_mode, xcb_drawable_t drawable,
       xcb_gcontext_t gc, uint32_t points_len, const
       xcb_point_t *points);

that return type? xcb_void_cookie_t. remember her, we come back to her later bestie 💖

---

🔥 REQUEST ARGUMENTS 🔥

• conn — your XCB connection to X11. the group chat you're sending all this through, basically 👑
• coordinate_mode — literally one of these two values, pick your fighter:
  • XCB_COORD_MODE_ORIGIN — treats all coordinates as relative to the origin. every single one, no exceptions, periodt.
  • XCB_COORD_MODE_PREVIOUS — treats all coordinates after the first as relative to the previous coordinate. so the first one's still on its own, and everything after is like "yeah I'm standing on the shoulders of the point before me" 🫶

TODO: NOT YET DOCUMENTED.

• drawable — TODO: NOT YET DOCUMENTED. 😭
• gc — TODO: NOT YET DOCUMENTED. 😭
• points_len — TODO: NOT YET DOCUMENTED. 😭
• points — TODO: NOT YET DOCUMENTED. 😭

ngl the docs really said "figure it out bestie" on like four of these, but the argument names are right there and they're not going anywhere 💀

---

🌈 DESCRIPTION 🌈

…and that's it. that's the whole description. the section exists, she showed up, she said nothing. iconic behaviour honestly. the description is empty. we move. 💅

---

⭐ RETURN VALUE ⭐

she returns an xcb_void_cookie_t. and because XCB loves to keep you on your toes, any errors have to be handled over in the event loop — not here, not now, later, in the loop, like a little surprise 🌸

if you'd rather deal with errors directly using xcb_request_check, then use xcb_poly_point_checked instead. same energy, different entry point. see xcb-requests(3) for all the deets on how that works 💖

---

💀 ERRORS 💀

this request does never generate any errors. zero. none. not a single one. she's unproblematic, she's low-drama, she ate and left no crumbs 🔥

---

🎀 SEE ALSO 🎀

nothing here bestie, the section is empty. enjoy the silence 🦋

---

🫶 AUTHOR 🫶

Generated from xproto.xml. if you've got corrections or improvements, hit up xcb@lists.freedesktop.org — they're literally waiting for your email, no cap 💜

---

and that's the whole page! xcb_poly_point(3) comes to you from X Version 11, running libxcb 1.17.0 — mwah, go draw some points bestie, you got this ✨💅🌸