Don't set current point to (0,0) in close_path.

The setting of current point to (0,0) is actually harmless, but it
definitely looks like a bug, (since after close_path the current point
is really the last move point).

We don't keep track of last move point here, nor do we even need to.
So we can be consistent with _cairo_path_fixed_close_path by not
adjusting current point at all, (the subsequent move_to coming right
behind the close_path will fix up the current point).
This commit is contained in:
Carl Worth 2006-08-18 06:31:15 -07:00
parent 53f74e59fa
commit c78c011017

View file

@ -125,9 +125,6 @@ _cpdc_close_path (void *closure)
cpdc->count += 1;
cpdc->current_point.x = 0;
cpdc->current_point.y = 0;
return CAIRO_STATUS_SUCCESS;
}
@ -304,9 +301,6 @@ _cpdp_close_path (void *closure)
cpdp->data += data->header.length;
cpdp->current_point.x = 0;
cpdp->current_point.y = 0;
return CAIRO_STATUS_SUCCESS;
}