Change all instances of UINT16_MAX to INT16_MAX to avoid new bug.

A recent renaming from CAIRO_MAXSHORT also changed the range of some
values from INT16_MAX to UINT16_MAX. The test suite shows one case
where this introduces a bug, (push/pop_group with SVG and RGB24
surfaces).

I haven't tracked the bug down, (presumably there's overflow of the
unsigned value at some point), but I'm now reverting this to avoid
triggering the bug.
This commit is contained in:
Carl Worth 2006-06-07 02:59:51 -07:00
parent 7f2cf378d5
commit 3690eeb44c
2 changed files with 4 additions and 4 deletions

View file

@ -551,8 +551,8 @@ _cairo_meta_surface_get_extents (void *abstract_surface,
{
rectangle->x = 0;
rectangle->y = 0;
rectangle->width = UINT16_MAX;
rectangle->height = UINT16_MAX;
rectangle->width = INT16_MAX;
rectangle->height = INT16_MAX;
return CAIRO_STATUS_SUCCESS;
}

View file

@ -1457,8 +1457,8 @@ _cairo_pattern_get_extents (cairo_pattern_t *pattern,
extents->x = 0;
extents->y = 0;
extents->width = UINT16_MAX;
extents->height = UINT16_MAX;
extents->width = INT16_MAX;
extents->height = INT16_MAX;
return CAIRO_STATUS_SUCCESS;
}