mirror of
https://gitlab.freedesktop.org/cairo/cairo.git
synced 2025-12-27 19:50:11 +01:00
a69335a84e
A common requirement is the fast upload of pixel data. In order to allocate the most appropriate image buffer, we need knowledge of the destination. The most obvious example is that we could use a shared-memory region for the image to avoid the transfer cost of uploading the pixels to the X server. Similarly, gl, win32, quartz... The other side of the equation is that for manual modification of a remote surface, it would be more efficient if we can create a similar image to reduce the transfer costs. This strategy is already followed for the destination fallbacks and this merely exposes the same capability for the application fallbacks. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> |
||
|---|---|---|
| .. | ||
| examples | ||
| .gitignore | ||
| cairo-script-file.c | ||
| cairo-script-hash.c | ||
| cairo-script-interpreter.c | ||
| cairo-script-interpreter.h | ||
| cairo-script-objects.c | ||
| cairo-script-operators.c | ||
| cairo-script-private.h | ||
| cairo-script-scanner.c | ||
| cairo-script-stack.c | ||
| COPYING | ||
| csi-bind.c | ||
| csi-exec.c | ||
| csi-replay.c | ||
| csi-trace.c | ||
| Makefile.am | ||
| Makefile.sources | ||
| Makefile.win32 | ||