From b0f65054b810d432238ff4986bee3f63e1fc46df Mon Sep 17 00:00:00 2001 From: M Joonas Pihlaja Date: Sun, 29 Aug 2010 00:03:07 +0300 Subject: [PATCH] subsurface: Add a note to the docs about usage restrictions. Make our assumptions about constructed subsurfaces explicit while we work out the correct semantics for the edge cases. --- src/cairo-surface-subsurface.c | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/cairo-surface-subsurface.c b/src/cairo-surface-subsurface.c index 96459a789..9b21fa65d 100644 --- a/src/cairo-surface-subsurface.c +++ b/src/cairo-surface-subsurface.c @@ -486,6 +486,11 @@ static const cairo_surface_backend_t _cairo_surface_subsurface_backend = { * directly onto the parent surface, i.e. with no further backend allocations, * double buffering or copies. * + * The semantics of subsurfaces have not been finalized yet + * unless the rectangle is in full device units, is contained within + * the extents of the target surface, and the target or subsurface's + * device transforms are not changed. + * * Return value: a pointer to the newly allocated surface. The caller * owns the surface and should call cairo_surface_destroy() when done * with it. @@ -493,6 +498,8 @@ static const cairo_surface_backend_t _cairo_surface_subsurface_backend = { * This function always returns a valid pointer, but it will return a * pointer to a "nil" surface if @other is already in an error state * or any other error occurs. + * + * Since: 1.10 **/ cairo_surface_t * cairo_surface_create_for_rectangle (cairo_surface_t *target,