cairo_gstate_t?

I know this has been discussed many many times, but I was thinking about it
again today.  I think we should model it like the cairo_path_t.  Ie, the
following API will be exposed:

cairo_gstate_t *
cairo_copy_gstate (cairo_t *cr);

cairo_gstate_t *
cairo_gstate_copy (cairo_gstate_t *gstate);

void
cairo_set_gstate (cairo_t *cr, cairo_gstate_t *gstate);

And perhaps:

void
cairo_push_gstate (cairo_t *cr, cairo_gstate_t *gstate);

cairo_gstate_t *
cairo_pop_gstate (cairo_t *cr);

void
cairo_gstate_reference (cairo_gstate_t *gstate)

void
cairo_gstate_destroy (cairo_gstate_t *gstate)


Thoughts?

behdad
--
cairo mailing list
[email protected]
http://lists.cairographics.org/mailman/listinfo/cairo