xcb_glx_get_minmax_parameteriv_data_end3
Part of xcb_glx_get_minmax_parameteriv(3).
Usage
Reply datastructure
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
uint8_t pad1
[4]
;
uint32_t n;
int32_t datum;
uint8_t pad2
[12]
;
Reply accessors
int32_t *xcb_glx_get_minmax_parameteriv_data(const
xcb_glx_get_minmax_parameteriv_request_t
*reply);
int xcb_glx_get_minmax_parameteriv_data_length(const
xcb_glx_get_minmax_parameteriv_reply_t
*reply);
xcb_generic_iterator_t xcb_glx_get_minmax_parameteriv_data_end(const
xcb_glx_get_minmax_parameteriv_reply_t
*reply);
Request arguments
- conn
-
The XCB connection to X11.
- context_tag
-
TODO: NOT YET DOCUMENTED.
- target
-
TODO: NOT YET DOCUMENTED.
- pname
-
TODO: NOT YET DOCUMENTED.
Reply fields
- response_type
-
The type of this reply, in this case XCB_GLX_GET_MINMAX_PARAMETERIV. This field is also present in the xcb_generic_reply_t and can be used to tell replies apart from each other.
- sequence
-
The sequence number of the last request processed by the X11 server.
- length
-
The length of the reply, in words (a word is 4 bytes).
- n
-
TODO: NOT YET DOCUMENTED.
- datum
-
TODO: NOT YET DOCUMENTED.
Overview
Return value
Returns an xcb_glx_get_minmax_parameteriv_cookie_t. Errors have to be handled when calling the reply function xcb_glx_get_minmax_parameteriv_reply.
If you want to handle errors in the event loop instead, use xcb_glx_get_minmax_parameteriv_unchecked. See xcb-requests(3) for details.
Errors
This request does never generate any errors.
History
- Arch Linux 2026-11-01 to Debian 13 (Trixie): the text shown here
- Debian 12 (Bookworm)
- Debian 11 (Bullseye)
- Debian 10 (Buster)
- Debian 9 (Stretch)