On 9/16/05, mental@...3... <mental@...3...> wrote:
When you're using miter joins, the necessary padding to the path bounding box will be the stroke width * the miter limit, instead of the stroke width.
That's the only adjustment required to fix the bug.
No. This will give much too big bbox inflation than necessary in the big majority of cases. It's extremely rare that the real object bbox srtetches to the entire stroke width * the miter limit. So compared to that, the current method (just adding stroke width) gives correct results in a much bigger % of cases, and when it's wrong, its error is much lower.
The only advantage of your method is that it always gives a _guaranteed_ inclusion (i.e. upper limit for the bbox), but I don't think we're interested in that.