[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cairo
Subject:    Re: [cairo] API proposal: Damage Tracking
From:       "Benjamin Otte" <otte () gnome ! org>
Date:       2008-12-11 9:34:37
Message-ID: a4ed255b0812110134r20829e38mcc302c6aa9e06f7d () mail ! gmail ! com
[Download RAW message or body]

On Thu, Dec 11, 2008 at 10:23 AM, Soeren Sandmann <sandmann@daimi.au.dk> wrote:
> At the summit, Carl suggested that we could make cairo_region_t
> public, then have API like this:
>
>    cairo_tracking_id_t
>    cairo_begin_tracking (cairo_t *cr,
>                          tracking_type_t type,
>                          cairo_region_t *region);
>
>    void
>    cairo_end_tracking (cairo_tracking_id_t id);
>
I have one problem with this API, namely attaching to a cairo_t as
opposed to attaching to a cairo_surface_t.
Using a cairo_t is fine if you're the only user, but I think libraries
that want to make use of damage tracking internally (take double
buffering with gdk_window_begin/end_paint for example) would want to
keep track of the surface they use for that purpose. Otherwise they
could only really make use of damage tracking if they only exported
cairo_t objects, which sounds very suboptimal to me.

Is there any reason to not track damage on surfaces instead?

Cheers,
Benjamin
_______________________________________________
cairo mailing list
cairo@cairographics.org
http://lists.cairographics.org/mailman/listinfo/cairo
[prev in list] [next in list] [prev in thread] [next in thread]