XCB_GLX_GET_QUERY_OBJECTUIV_ARB_DATA_LENGTH(3)

πŸ“¦
version 1.17.0 Β· 4 versions
, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, centos-stream 10, debian trixie, fedora 43, fedora 44, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– xcb_glx_get_query_objectuiv_arb β€” XCB Requests ✨

okay so bestie, welcome to the group chat where we talk about a very specific little XCB request πŸ’… this page lives in the XCB Requests manual, and honestly? it's giving "barely documented but we love her anyway" energy. no cap.


🌸 NAME 🌸

xcb_glx_get_query_objectuiv_arb β€” literally no description given, bestie. that's the whole name. we move. 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

#include <xcb/glx.h>

✨ Request function ✨

xcb_glx_get_query_objectuiv_arb_cookie_t
       xcb_glx_get_query_objectuiv_arb(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag, uint32_t id, uint32_t pname);

πŸŽ€ Reply datastructure πŸŽ€

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

🌈 Reply function 🌈

xcb_glx_get_query_objectuiv_arb_reply_t
       *xcb_glx_get_query_objectuiv_arb_reply(xcb_connection_t *conn,
       xcb_glx_get_query_objectuiv_arb_cookie_t cookie,
       xcb_generic_error_t **e);

πŸ’œ Reply accessors πŸ’œ

uint32_t *xcb_glx_get_query_objectuiv_arb_data(const
       xcb_glx_get_query_objectuiv_arb_request_t *reply);

int xcb_glx_get_query_objectuiv_arb_data_length(const
       xcb_glx_get_query_objectuiv_arb_reply_t *reply);

xcb_generic_iterator_t xcb_glx_get_query_objectuiv_arb_data_end(const
       xcb_glx_get_query_objectuiv_arb_reply_t *reply);

πŸ”₯ REQUEST ARGUMENTS πŸ”₯

the way that every single one of these is "TODO: NOT YET DOCUMENTED"… not me crying 😭 but fr fr here's the roster:

  • conn β€” the XCB connection to X11. your little lifeline to the server, bestie 🫢
  • context_tag β€” TODO: NOT YET DOCUMENTED. yes really. nobody wrote it. πŸ’€
  • id β€” TODO: NOT YET DOCUMENTED. iconic of them tbh πŸ™ˆ
  • pname β€” TODO: NOT YET DOCUMENTED. the trilogy of mystery πŸŽ€

⭐ REPLY FIELDS ⭐

  • response_type β€” the type of this reply, in this case XCB_GLX_GET_QUERY_OBJECTUIV_ARB. this field is also present in the xcb_generic_reply_t and can be used to tell replies apart from each other. vibe check: use it to know which reply is which πŸ‘‘
  • sequence β€” the sequence number of the last request processed by the X11 server. tracking the timeline, main character energy ✨
  • length β€” the length of the reply, in words (a word is 4 bytes). quick maths, no cap πŸ’…
  • n β€” TODO: NOT YET DOCUMENTED. mystery number one πŸ¦‹
  • datum β€” TODO: NOT YET DOCUMENTED. mystery number two 🌸

πŸ’« DESCRIPTION πŸ’«

nothing here. literally nothing. the void. the silence. we stan an empty section πŸ•³οΈβœ¨


🌟 RETURN VALUE 🌟

returns an xcb_glx_get_query_objectuiv_arb_cookie_t. errors have to be handled when calling the reply function xcb_glx_get_query_objectuiv_arb_reply. πŸ“

if you want to handle errors in the event loop instead, use xcb_glx_get_query_objectuiv_arb_unchecked. see xcb-requests(3) for details. periodt. πŸ’…


πŸŽ€ ERRORS πŸŽ€

this request does never generate any errors. she's unproblematic, she's perfect, she ate and left no crumbs πŸ”₯


🧚 SEE ALSO 🧚

nothing listed here either, bestie. it's just vibes 🌈


πŸ’œ AUTHOR πŸ’œ

generated from glx.xml. contact xcb@lists.freedesktop.org for corrections and improvements. go off, glx.xml πŸ‘‘


and that's the whole page, bestie!! 🫢 this manual page came to you from X Version 11, running libxcb 1.17.0 β€” mwah, slay, bye πŸ’–βœ¨πŸŽ€