|
NAMExcb_x_print_print_get_document_data -SYNOPSIS#include <xcb/xprint.h>Request functionxcb_x_print_print_get_document_data_cookie_t xcb_x_print_print_get_document_data(xcb_connection_t *conn, xcb_x_print_pcontext_t context, uint32_t max_bytes); Reply datastructuretypedef struct xcb_x_print_print_get_document_data_reply_t { uint8_t response_type; uint8_t pad0; uint16_t sequence; uint32_t length; uint32_t status_code; uint32_t finished_flag; uint32_t dataLen; uint8_t pad1[12]; } xcb_x_print_print_get_document_data_reply_t; Reply functionxcb_x_print_print_get_document_data_reply_t *xcb_x_print_print_get_document_data_reply(xcb_connection_t *conn, xcb_x_print_print_get_document_data_cookie_t cookie, xcb_generic_error_t **e); Reply accessorsuint8_t *xcb_x_print_print_get_document_data_data(const xcb_x_print_print_get_document_data_request_t *reply); int xcb_x_print_print_get_document_data_data_length(const xcb_x_print_print_get_document_data_reply_t *reply); xcb_generic_iterator_t
xcb_x_print_print_get_document_data_data_end(const
xcb_x_print_print_get_document_data_reply_t *reply);
REQUEST ARGUMENTS
REPLY FIELDS
DESCRIPTIONRETURN VALUEReturns an xcb_x_print_print_get_document_data_cookie_t. Errors have to be handled when calling the reply function xcb_x_print_print_get_document_data_reply.If you want to handle errors in the event loop instead, use xcb_x_print_print_get_document_data_unchecked. See xcb-requests(3) for details. ERRORSThis request does never generate any errors.SEE ALSOAUTHORGenerated from xprint.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.
Visit the GSP FreeBSD Man Page Interface. |