Re: Question about extents and transformations

Hi,

On 09.12.19 11:04, [email protected] wrote:
[...]
> The documentation for cairo_path_extents() states: =93Computes a bounding
> box in user-space coordinates=94, that=92s why I expect the extents of a
> given path to always be the same, whichever transformation might be
> applied.

What the implementation actually does: It computes a (tight?) bounding
box in device space and then transforms that to user-space coordinates.
This explains the behaviour that you get, I think.

> It appears to be the case for scaling and translations, but rotation gives
> me different extents. Am I missing something or is this a bug?

Well, the documentation only says that you get "a" bounding box, not
"the tightest possible" bounding box. So, I would say that this is not a
bug and then I would go ahead and bury my head in the sand...

Cheers,
Uli

-- =

99 little bugs in the code
99 little bugs in the code
Take one down, patch it around
117 little bugs in the code
  -- @irqed
-- =

cairo mailing list
[email protected]
https://lists.cairographics.org/mailman/listinfo/cairo