summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2012-06-08 17:20:32 +0100
committerChris Wilson <chris@chris-wilson.co.uk>2012-06-08 17:26:11 +0100
commit1bc696a8fda55ee75139f7d0123d348bbd96d2af (patch)
treedf346ebea21bd8fdcc3452668ffa83d92e1d1a45
parent37532b47c0ef6528fb6696fe97be337d9ad0a900 (diff)
spans-compositor: After polygon intersection the fill rule is always non-zero
As it turns out due to the rules of polygon intersection, there is never any overlapping spans so the choice is arbitrary. However, lets be consistent with the rest of the code. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
-rw-r--r--src/cairo-spans-compositor.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/src/cairo-spans-compositor.c b/src/cairo-spans-compositor.c
index 6cc9a7b0..602d6a64 100644
--- a/src/cairo-spans-compositor.c
+++ b/src/cairo-spans-compositor.c
@@ -934,6 +934,8 @@ clip_and_composite_polygon (const cairo_spans_compositor_t *compositor,
status = trim_extents_to_polygon (extents, polygon);
if (unlikely (status))
return status;
+
+ fill_rule = CAIRO_FILL_RULE_WINDING;
} else {
_cairo_polygon_fini (&clipper);
}