[cairo] On copying graphics state and path between contexts (was:
cworth at cworth.org
Fri Sep 22 11:03:29 PDT 2006
On Fri, 22 Sep 2006 08:49:19 -0700, "Mike Emmel" wrote:
> Finally of course there is no efficient way to copy the path between cairo_t's
> In general one programing style I'd love to use is to create a cairo_t
> thats abstract
> and not attached to a real surface ( I do this now with a 1,1 image
> surface ) then
> use it as a template for a real surface. save and restors on the template path
> should protect it from modification.
First, I think it's important to point out the separation between the
(stacked) graphics state and the path within the cairo_t context. The
graphics state does _not_ include the path, and the graphics state
exists on a stack which can be manipulated with cairo_save and
The path is separate from the graphics state, and is unaffected by
the cairo_save and cairo_restore operations.
Currently, one can copy the path from one context to another with
cairo_copy_path and cairo_append_path. Those two function calls do do
some conversion in addition to copying. I'd be glad to consider a
proposal for more direct copying of a path from one context to another
along with some direct evidence that the conversion of
copy/append_path is causing a "real-world" performance problem.
As for copying the graphics state, most of it can be copied now in a
piecemeal fashion, with the various get/set functions, (and hopefully
with Vlad's recent addition of various get functions it's now possible
to copy all of the graphics state). Admittedly, that's not a very
convenient thing to do, and we've had proposals (and even
implementations) for things like cairo_copy and
The cairo_save_state/cairo_restore_state proposal was the most recent
and I rather liked it:
But the discussion pretty much stopped right after that when Owen
asked for a non-trivial use case for the new API and nobody ever
> cairo_set_destination_surface(cairo_t* template,cairo_surface_t* dest);
Before cairo 1.0 we did have a way to change the destination
> cairo_restor(cr); //restores cr to last state.
and we did have the destination surface as part of the graphics state
manipulated with save/restore.
We found there was some dramatic conceptual simplification when we
eliminated the ability to change the destination surface and made that
instead an immutable property of a cairo_t context.
One example of the confusion is the strong dependence of a some
elements of the graphics state (such as the transformation matrix) on
the destination surface. For instance, should switching a
screen-display surface to a PDF surface also change to the default,
identity transformation matrix? Should it reset other parts of the
It's much more obvious how things work when a separate context, with
its own graphics state is used for each separate destination surface.
As for the need to create a 1x1 dummy surface to do some cairo
operations that don't require a destination surface, that is a bit
annoying. We've been improving this in some ways by the addition of
things like cairo_scaled_font_text_extents so that it's now possible
to measure text and know how big the destination surface will need to
be, without having to create a dummy surface for the measurement.
Path construction does still require a surface, but I don't see that
as nearly as much of a problem, (though it might still be necessary to
use a dummy surface to measure the extents of a path before creating a
surface that will cache a rendering of it). But cairo really isn't
trying to provide data structures for holding on to and manipulating
paths. So I think it would be a mistake to add a bunch of API calls
that would give that appearance. Users of cairo really should use
their own structures for holding on to their own geometry and should
simply create paths in cairo at the they are ready to draw them.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/cairo/attachments/20060922/4f51a3ce/attachment.pgp
More information about the cairo