summaryrefslogtreecommitdiff
path: root/doc/public/html/cairo-cairo-device-t.html
diff options
context:
space:
mode:
authorCyril Brulebois <kibi@debian.org>2011-06-20 01:53:48 +0200
committerCyril Brulebois <kibi@debian.org>2011-06-20 01:53:48 +0200
commit33cc97022c22336d56b8875d041b55877199e9e7 (patch)
tree4d31aabc4d13416d59b4acc1934c16eb973eddad /doc/public/html/cairo-cairo-device-t.html
parent71431660470357a652819295118cb92d0e5d0e80 (diff)
Import upstream release 1.11.21.11.2upstream-experimental
Diffstat (limited to 'doc/public/html/cairo-cairo-device-t.html')
-rw-r--r--doc/public/html/cairo-cairo-device-t.html8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/public/html/cairo-cairo-device-t.html b/doc/public/html/cairo-cairo-device-t.html
index 9238333..97a84d2 100644
--- a/doc/public/html/cairo-cairo-device-t.html
+++ b/doc/public/html/cairo-cairo-device-t.html
@@ -132,8 +132,8 @@ surfaces of that type.
A <a class="link" href="cairo-cairo-device-t.html#cairo-device-t" title="cairo_device_t"><span class="type">cairo_device_t</span></a> represents the driver interface for drawing
operations to a <a class="link" href="cairo-cairo-surface-t.html#cairo-surface-t" title="cairo_surface_t"><span class="type">cairo_surface_t</span></a>. There are different subtypes of
<a class="link" href="cairo-cairo-device-t.html#cairo-device-t" title="cairo_device_t"><span class="type">cairo_device_t</span></a> for different drawing backends; for example,
-<code class="function">cairo_xcb_device_create()</code> creates a device that wraps the connection
-to an X Windows System using the XCB library.
+<code class="function">cairo_egl_device_create()</code> creates a device that wraps an EGL display and
+context.
</p>
<p>
The type of a device can be queried with <a class="link" href="cairo-cairo-device-t.html#cairo-device-get-type" title="cairo_device_get_type ()"><code class="function">cairo_device_get_type()</code></a>.
@@ -303,7 +303,8 @@ The various <a class="link" href="cairo-cairo-device-t.html#cairo-device-t" titl
any type, but some backends also provide type-specific functions
that must only be called with a device of the appropriate
type. These functions have names that begin with
-cairo_<span class="emphasis"><em>type</em></span>_device such as <code class="function">cairo_xcb_device_debug_set_render_version()</code>.
+<code class="literal">cairo_<span class="emphasis"><em>type</em></span>_device</code> such as
+<code class="function">cairo_xcb_device_debug_cap_xrender_version()</code>.
</p>
<p>
The behavior of calling a type-specific function with a surface of
@@ -343,7 +344,6 @@ New entries may be added in future versions.
<tr>
<td><p><a name="CAIRO-DEVICE-TYPE-XML:CAPS"></a><span class="term"><code class="literal">CAIRO_DEVICE_TYPE_XML</code></span></p></td>
<td>The surface is of type XML
- <a class="link" href="cairo-cairo-surface-t.html#cairo-surface-create-for-rectangle" title="cairo_surface_create_for_rectangle ()"><code class="function">cairo_surface_create_for_rectangle()</code></a>
</td>
</tr>
</tbody>