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:

196714

userrating:

average rating: 1.7 (102 votes) (1=very good 6=terrible)

May 25th. 2007:

Words

486

Views

252324

why adblockers are bad

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

words:

161

views:

141294

userrating:

average rating: 1.4 (42 votes) (1=very good 6=terrible)

April, 26th. 2006:

Words

Views

101157

New subdomain: toolsntoys.linuxhowtos.org

You are here: manpages

xcb_randr_get_panning

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

NAME

xcb_randr_get_panning -

SYNOPSIS

#include <xcb/randr.h>

Request function

: xcb_randr_get_panning_cookie_t xcb_randr_get_panning(xcb_connection_t *conn, xcb_randr_crtc_t crtc);

Reply datastructure


typedef struct xcb_randr_get_panning_reply_t {
    uint8_t         response_type;
    uint8_t         status;
    uint16_t        sequence;
    uint32_t        length;
    xcb_timestamp_t timestamp;
    uint16_t        left;
    uint16_t        top;
    uint16_t        width;
    uint16_t        height;
    uint16_t        track_left;
    uint16_t        track_top;
    uint16_t        track_width;
    uint16_t        track_height;
    int16_t         border_left;
    int16_t         border_top;
    int16_t         border_right;
    int16_t         border_bottom;
} xcb_randr_get_panning_reply_t;

Reply function

: xcb_randr_get_panning_reply_t *xcb_randr_get_panning_reply(xcb_connection_t *conn, xcb_randr_get_panning_cookie_t cookie, xcb_generic_error_t **e);

REQUEST ARGUMENTS

conn: The XCB connection to X11.
crtc: TODO: NOT YET DOCUMENTED.

REPLY FIELDS

response_type: The type of this reply, in this case XCB_RANDR_GET_PANNING. 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).
status: TODO: NOT YET DOCUMENTED.
timestamp: TODO: NOT YET DOCUMENTED.
left: TODO: NOT YET DOCUMENTED.
top: TODO: NOT YET DOCUMENTED.
width: TODO: NOT YET DOCUMENTED.
height: TODO: NOT YET DOCUMENTED.
track_left: TODO: NOT YET DOCUMENTED.
track_top: TODO: NOT YET DOCUMENTED.
track_width: TODO: NOT YET DOCUMENTED.
track_height: TODO: NOT YET DOCUMENTED.
border_left: TODO: NOT YET DOCUMENTED.
border_top: TODO: NOT YET DOCUMENTED.
border_right: TODO: NOT YET DOCUMENTED.
border_bottom: TODO: NOT YET DOCUMENTED.