From 1bc696a8fda55ee75139f7d0123d348bbd96d2af Mon Sep 17 00:00:00 2001 From: Chris Wilson Date: Fri, 8 Jun 2012 17:20:32 +0100 Subject: [PATCH] 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 --- src/cairo-spans-compositor.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/cairo-spans-compositor.c b/src/cairo-spans-compositor.c index 6cc9a7b00..602d6a647 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); }