www.LinuxHowtos.org howtos, tips&tricks and tutorials for linux

from small one page howto to huge articles all in one place

Other .linuxhowtos.org sites:toolsntoys.linuxhowtos.org
gentoo.linuxhowtos.org

poll results

Last additions:

using iotop to find disk usage hogs

words:

887

views:

206223

userrating:

average rating: 1.5 (158 votes) (1=very good 6=terrible)

May 25th. 2007:

Words

486

Views

257051

why adblockers are bad

Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

words:

161

views:

147700

userrating:

average rating: 1.2 (114 votes) (1=very good 6=terrible)

April, 26th. 2006:

Words

Views

105926

New subdomain: toolsntoys.linuxhowtos.org

You are here: manpages

xcb_randr_get_provider_property

Section: XCB Requests (3)
Updated: libxcb 1.12
Index Return to Main Contents

NAME

xcb_randr_get_provider_property -

SYNOPSIS

#include <xcb/randr.h>

Request function

: xcb_randr_get_provider_property_cookie_t xcb_randr_get_provider_property(xcb_connection_t *conn, xcb_randr_provider_t provider, xcb_atom_t property, xcb_atom_t type, uint32_t long_offset, uint32_t long_length, uint8_t _delete, uint8_t pending);

Reply datastructure


typedef struct xcb_randr_get_provider_property_reply_t {
    uint8_t    response_type;
    uint8_t    format;
    uint16_t   sequence;
    uint32_t   length;
    xcb_atom_t type;
    uint32_t   bytes_after;
    uint32_t   num_items;
    uint8_t    pad0[12];
} xcb_randr_get_provider_property_reply_t;

Reply function

: xcb_randr_get_provider_property_reply_t *xcb_randr_get_provider_property_reply(xcb_connection_t *conn, xcb_randr_get_provider_property_cookie_t cookie, xcb_generic_error_t **e);

Reply accessors

: void *xcb_randr_get_provider_property_data(const xcb_randr_get_provider_property_request_t *reply);
: int xcb_randr_get_provider_property_data_length(const xcb_randr_get_provider_property_reply_t *reply);
: xcb_generic_iterator_t xcb_randr_get_provider_property_data_end(const xcb_randr_get_provider_property_reply_t *reply);

REQUEST ARGUMENTS

conn: The XCB connection to X11.
provider: TODO: NOT YET DOCUMENTED.
property: TODO: NOT YET DOCUMENTED.
type: TODO: NOT YET DOCUMENTED.
long_offset: TODO: NOT YET DOCUMENTED.
long_length: TODO: NOT YET DOCUMENTED.
_delete: TODO: NOT YET DOCUMENTED.
pending: TODO: NOT YET DOCUMENTED.

REPLY FIELDS

response_type: The type of this reply, in this case XCB_RANDR_GET_PROVIDER_PROPERTY. 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).
format: TODO: NOT YET DOCUMENTED.
type: TODO: NOT YET DOCUMENTED.
bytes_after: TODO: NOT YET DOCUMENTED.
num_items: TODO: NOT YET DOCUMENTED.

DESCRIPTION

RETURN VALUE

Returns an xcb_randr_get_provider_property_cookie_t. Errors have to be handled when calling the reply function xcb_randr_get_provider_property_reply.

If you want to handle errors in the event loop instead, use xcb_randr_get_provider_property_unchecked. See xcb-requests(3) for details.