| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Fix some enum mixups, mostly cairo_status_t vs cairo_test_status_t.
|
| |
|
|
| |
due to a subsurface snapshot bug causing recursion in the pdf backend.
|
| |
|
|
|
|
|
|
|
|
| |
Carefully handle subsurfaces of a recording surface through the analysis
and paginated surfaces so that we can generate a native pattern for the
vector backends, demonstrated by the PostScript backend.
Nothing remarkable, just a lot of bookkeeping to track the wrapped
surface types and to apply the correct offsets when generating the
subsurface pattern.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
After a renewed discussion, it was pointed out that the API in Cairo was
not restrictive and by using doubles we would be consisted with the rest
of the API. Thus prompting the name change to
cairo_surface_create_for_rectangle()
similar to cairo_rectangle().
And document the public API.
|
|
|
A subsurface is a region of another surface that may be used either to
restrict the writable area of a context or the readable extents of a
source. Whilst writing, access to the exterior of the subsurface is
prevented via clipping and when used as a source reads from the exterior
of the subsurface are governed via the extend mechanism of the pattern.
|
