Hallo, dies ist ein Test.

PWD: /www/data-lst1/unixsoft/unixsoft/kaempfer/.public_html

Running in File Mode
Relative path: ././../../../../../../usr/man/man3xcb/xcb-examples.3xcb
Real path: /usr/share/man/man3xcb/xcb-examples.3xcb
Zurück

'\" te .TH xcb-examples 3xcb "libxcb 1.15" "X Version 11" "XCB examples" .ad l .SH NAME xcb-examples \- manpage examples .SH DESCRIPTION Many of the XCB manpages contain example code. These examples intend to explain how to use one particular part of XCB. They almost never represent a standalone (or even useful) program - X11 programs are relatively involved and thus beyond the scope of a manpage example. .SH ENVIRONMENT Every example assumes you have an \fIxcb_connection\fP and possibly other variables at hand. For illustrating how \fIxcb_get_property\fP works, you need the window of which you want to get the property, for example. To make it clear that these variables are your responsibility, these examples consist of a single function which takes the necessary variables as parameters. .SH FLUSHING Flushing means calling \fIxcb_flush\fP to clear the XCB-internal write buffer and send all pending requests to the X11 server. You don't explicitly need to flush before using a reply function (like \fIxcb_query_pointer_reply\fP), but you do need to flush before entering the event loop of your program. There are only two cases when XCB flushes by itself. The first case is when its write buffer becomes full, the second case is when you are asking for the reply of a request which wasn't flushed out yet (like \fIxcb_query_pointer_reply\fP). This last point also includes xcb_request_check(). Please note that waiting for an event does \fBNOT\fP flush. Examples generally include the \fIxcb_flush\fP call where appropriate (for example after setting a property). Therefore, including these functions and calling them in your application should just work. However, you might get better results when flushing outside of the function, depending on the architecture of your program. .SH COMPILATION If an example does not compile (without warnings) when using \fI-std=c99\fP, that is considered a documentation bug. Similarly, not handling errors or leaking memory is also considered a documentation bug. Please inform us about it on xcb@lists.freedesktop.org. .SH CODING STYLE Every example uses 4 spaces for indentation. Comments are in asterisks, like /* this */. No line is longer than 80 characters (including indentation). .\" Oracle has added the ARC stability level to this manual page .SH ATTRIBUTES See .BR attributes (7) for descriptions of the following attributes: .sp .TS box; cbp-1 | cbp-1 l | l . ATTRIBUTE TYPE ATTRIBUTE VALUE = Availability x11/library/libxcb = Stability Volatile .TE .PP .SH SEE ALSO .BR xcb_connect (3xcb), .BR xcb_get_property (3xcb), .BR xcb_flush (3xcb) .SH AUTHOR Michael Stapelberg <michael+xcb at stapelberg dot de> .SH NOTES .\" Oracle has added source availability information to this manual page Source code for open source software components in Oracle Solaris can be found at https://www.oracle.com/downloads/opensource/solaris-source-code-downloads.html. This software was built from source available at https://github.com/oracle/solaris-userland. The original community source was downloaded from ['https://www.x.org/releases/individual/xcb/libxcb-1.15.tar.xz', 'https://xcb.freedesktop.org//dist/xcb-proto-1.15.2.tar.xz']. Further information about this software can be found on the open source community website at http://xcb.freedesktop.org/.