xcb_ungrab_pointer(3)

✨ xcb_ungrab_pointer(3) ✨

okay bestie, sit down, hydrate, and let me tell you about xcb_ungrab_pointer from the XCB Requests fam 💖 this is the one that hands the pointer back to the universe.

---

🌸 NAME 🌸

xcb_ungrab_pointer — release the pointer 🫶

---

🎀 SYNOPSIS 🎀

#include <xcb/xproto.h>

💫 Request function

xcb_void_cookie_t xcb_ungrab_pointer(xcb_connection_t *conn,
       xcb_timestamp_t time);

---

🦋 REQUEST ARGUMENTS 🦋

• conn — bestie this is just your XCB connection to X11. the line to the server. the situationship. 💜
• time — a timestamp, and it's here to avoid race conditions when you're running X over the network. no cap, this one matters:

the pointer will not be released if time is earlier than the last-pointer-grab time, or later than the current X server time. it's giving "goldilocks zone" fr fr 😭

---

🌈 DESCRIPTION 🌈

This releases the pointer and any queued events — but only if you actively grabbed the pointer before, using xcb_grab_pointer, xcb_grab_button, or within a normal button press. iykyk. 👑

EnterNotify and LeaveNotify events are generated. yes queen, the events are eventing. ✨

---

💅 RETURN VALUE 💅

Returns an xcb_void_cookie_t. Errors (if there are any at all) have to be handled in the event loop. that's just how the cookie crumbles 🍓

If you'd rather handle errors directly with xcb_request_check instead, use xcb_ungrab_pointer_checked. See xcb-requests(3) for the details, bestie. 🎀

---

💀 ERRORS 💀

This request does never generate any errors.

not a single one. iconic behaviour honestly. no drama, no crumbs, just peace 🧚

---

⭐ SEE ALSO ⭐

• xcb-requests(3)
• xcb_enter_notify_event_t(3)
• xcb_grab_button(3)
• xcb_grab_pointer(3)
• xcb_leave_notify_event_t(3)

---

🫶 AUTHOR 🫶

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

---

okay that's the whole page, you ate that 🍽️✨

X Version 11, from libxcb 1.17.0 — mwah, love u, go ungrab some pointers 💖🦋🌸 periodt.