mirror of
https://gitlab.freedesktop.org/cairo/cairo.git
synced 2026-05-02 07:18:05 +02:00
951a3dd9a7
The default RGB colorspace must be converted to the GPU's colorspace
using CGColorTransformConvertUsingCMSConverter. Profiling has shown this
function to consume as much as 48% of a redraw cycle in gdk-quartz.
There seems to be no named colorspace that matches the one stored on the
display, so we use the one associated with the main display. This has
some risks for users with multiple monitors but in testing with my own
two-monitor setup, one of which is HDR and the other not, the colorspace
was the same for both.
This is applied to quartz surfaces created with
cairo_quartz_surface_create(); surfaces created with
cairo_quartz_surface_create_for_cg_context will inherit the colorspace
from the context.
In order to generate PNGs that look right I've converted the
existing debugging functions for writing a quartz surface to png
into private functions and wired cairo-boilerplate-quartz to use
them. Using the generic cairo routine produced washed-out PNGs.
Fixes https://gitlab.freedesktop.org/cairo/cairo/-/issues/330
|
||
|---|---|---|
| .. | ||
| .gitignore | ||
| cairo-boilerplate-getopt.c | ||
| cairo-boilerplate-getopt.h | ||
| cairo-boilerplate-pdf.c | ||
| cairo-boilerplate-private.h | ||
| cairo-boilerplate-ps.c | ||
| cairo-boilerplate-quartz.c | ||
| cairo-boilerplate-scaled-font.h | ||
| cairo-boilerplate-script.c | ||
| cairo-boilerplate-svg.c | ||
| cairo-boilerplate-system.c | ||
| cairo-boilerplate-system.h | ||
| cairo-boilerplate-test-surfaces.c | ||
| cairo-boilerplate-win32-printing.c | ||
| cairo-boilerplate-win32.c | ||
| cairo-boilerplate-xcb.c | ||
| cairo-boilerplate-xlib.c | ||
| cairo-boilerplate-xlib.h | ||
| cairo-boilerplate.c | ||
| cairo-boilerplate.h | ||
| check-link.c | ||
| make-cairo-boilerplate-constructors.py | ||
| make-cairo-boilerplate-constructors.sh | ||
| meson.build | ||
| README | ||
This directory provides code that is common to both of cairo's tests suites: * The test suite for correctness in test/ * The test suite for performance in perf/ We call it boilerplate as it consists primarily of the boilerplate code necessary for initializing a backend in order to create a surface for that backend. The code here just might be useful for someone looking to get started writing cairo code to use a particular backend, (but there are no promises that the boilerplate code found here for any particular backend is exemplary).