[cairo] Clip region problems
spitzak at d2.com
Wed May 18 18:02:02 PDT 2005
Owen Taylor wrote:
> On Wed, 2005-05-18 at 15:56 -0700, Bill Spitzak wrote:
>>You should allow any number
>>of readers at the same time on any cairo_surface_t as long as no writer
> This would require quite a bit of complexity, since we temporarily
> modify internal attributes like filter and transform when using a
> surface as a source.
You are right. Never mind. No more than one user is allowed at any time
>>Wasn't there also a plan to make cairo_t and cairo_surface_t the same
>>object (ie cairo_create(surface) would not exist, instead the surface
>>itself can be used).
> This idea was rejected as too big a change at this point (and also quite
> likely not a good idea.)
Is there an interface to extract the cairo_surface_t from a cairo_t?
That would avoid the extra pointer, which I don't like because it
implies that they are independent of each other.
More information about the cairo