diff options
| author | Travis Spencer <tspencer@cs.pdx.edu> | 2005-07-31 08:01:01 -0800 |
|---|---|---|
| committer | Travis Spencer <tspencer@cs.pdx.edu> | 2005-07-31 08:01:01 -0800 |
| commit | db1e6df5d7f63bfc149f781b8b9703dc3d031933 (patch) | |
| tree | 3d376ef6f54a7905ef5aae80f6f6d7c00d35e071 /XCBConnectionOfDisplay.mdwn | |
| parent | 2583e4b6062c060ca265881453bee8ec2fd62223 (diff) | |
XCBConnectionOfDisplay
Diffstat (limited to 'XCBConnectionOfDisplay.mdwn')
| -rw-r--r-- | XCBConnectionOfDisplay.mdwn | 8 |
1 files changed, 3 insertions, 5 deletions
diff --git a/XCBConnectionOfDisplay.mdwn b/XCBConnectionOfDisplay.mdwn index 5f98c32..582665e 100644 --- a/XCBConnectionOfDisplay.mdwn +++ b/XCBConnectionOfDisplay.mdwn @@ -1,10 +1,8 @@ -# XCBConnectionOfDisplay - -## Function Prototype +# Function Prototype XCBConnection *XCBConnectionOfDisplay(Display *dpy); -## Example +# Example #include <X11/xcl.h> #include <stdlib.h> @@ -64,7 +62,7 @@ Some salient points in this example include the following: Though this example is contrived, `XCBConnectionOfDisplay` is an esential part of the porting process. For example, say you have some function that takes a `Display` object. You can leave the prototype unchanged, in the body of the function cast it to an `XCBConnection`, and port only that function. The rest of the code can remain unchanged. In this way, the process of converting the application to use XCB is staggered as necessary, time, knowledge, and knowledge permit. -## See Also +# See Also - [[XcbPorting]] - [[XCBConnection|XcbApi]] |