xcb_glx_get_lightfv(3)

💅 xcb_glx_get_lightfv(3) — XCB Requests, bestie edition

okay so you're looking at xcb_glx_get_lightfv(3) from the XCB Requests fam — it's the libxcb way of asking the X server for light parameter values over GLX. pull up a chair, we're doing this together 🫶

---

✨ NAME ✨

xcb_glx_get_lightfv — that's it, that's the name. the manpage really said "no description, figure it out" 💀 (the original NAME section is literally empty, no cap).

---

🌸 SYNOPSIS 🌸

first, the include. gotta get it in there:

#include <xcb/glx.h>

🎀 Request function

xcb_glx_get_lightfv_cookie_t xcb_glx_get_lightfv(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag, uint32_t light,
       uint32_t pname);

🦋 Reply datastructure

typedef struct xcb_glx_get_lightfv_reply_t {
    uint8_t           response_type;
    uint8_t           pad0;
    uint16_t          sequence;
    uint32_t          length;
    uint8_t           pad1[4];
    uint32_t          n;
    xcb_glx_float32_t datum;
    uint8_t           pad2[12];
} xcb_glx_get_lightfv_reply_t;

🧚 Reply function

xcb_glx_get_lightfv_reply_t
       *xcb_glx_get_lightfv_reply(xcb_connection_t *conn,
       xcb_glx_get_lightfv_cookie_t cookie, xcb_generic_error_t **e);

👑 Reply accessors

xcb_glx_float32_t *xcb_glx_get_lightfv_data(const
       xcb_glx_get_lightfv_request_t *reply);

int xcb_glx_get_lightfv_data_length(const xcb_glx_get_lightfv_reply_t
       *reply);

xcb_generic_iterator_t xcb_glx_get_lightfv_data_end(const
       xcb_glx_get_lightfv_reply_t *reply);

---

💖 REQUEST ARGUMENTS 💖

• conn — the XCB connection to X11. your lil hotline to the server, the main character of every XCB call fr fr.
• context_tag — TODO: NOT YET DOCUMENTED. yeah. the docs left us on read 😭 no explanation given, we simply do not know.
• light — TODO: NOT YET DOCUMENTED. same situation, bestie. the mystery continues 🙈.
• pname — TODO: NOT YET DOCUMENTED. three for three, the manpage is giving "we'll tell you later" energy 💀.

not me having to type "TODO: NOT YET DOCUMENTED" three times in a row. iconic of the docs honestly.

---

⭐ REPLY FIELDS ⭐

• response_type — the type of this reply, and in this case it's XCB_GLX_GET_LIGHTFV. this field also lives in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other. vibe check your replies, basically ✨
• sequence — the sequence number of the last request the X11 server actually processed.
• length — how long the reply is, in words. and a word is 4 bytes, just so we're clear 📏.
• n — TODO: NOT YET DOCUMENTED. again 😭.
• datum — TODO: NOT YET DOCUMENTED. yeah. we're all just out here guessing, lowkey.

---

🌈 DESCRIPTION 🌈

...nothing. there is genuinely nothing here. the DESCRIPTION section of this page is completely empty. an absolute void. she said "no thoughts, head empty" and meant it 💀

the original page has no description text. so like. that's the tea. nothing invented, nothing added. periodt.

---

🔥 RETURN VALUE 🔥

you get back an xcb_glx_get_lightfv_cookie_t. 🍪

errors? you handle those when you call the reply function, xcb_glx_get_lightfv_reply.

if you'd rather deal with errors in the event loop instead, use xcb_glx_get_lightfv_unchecked. see xcb-requests(3) for the deets 🫶

---

💀 ERRORS 💀

this request does never generate any errors. not one. zero. clean sheet, glowing skin, no drama. slay 💅

---

🍓 SEE ALSO 🍓

nothing listed, bestie. the SEE ALSO section is empty. we're on our own out here 😭 (there is no SEE ALSO reference on this page — that's the whole truth).

---

💜 AUTHOR 💜

Generated from glx.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. so if something's wrong, that's the inbox, not mine 🌸

---

and that's the whole page, bestie!! you ate, you read the whole manpage, main character energy only 👑

X Version 11 · libxcb 1.17.0 · bye pookie, go write some XCB code 💖✨🦋