New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bounds for SvgPath don't take transforms into account #830
Labels
Comments
birneamstiel
changed the title
Bounds for SvgPath does't take transforms into account
Bounds for SvgPath don't take transforms into account
Feb 19, 2021
Sorry for the long delay... |
H1Gdev
added a commit
to H1Gdev/SVG
that referenced
this issue
Oct 17, 2021
mrbean-bremen
pushed a commit
that referenced
this issue
Oct 17, 2021
* Add test. * Fixes #830 'Bounds for SvgPath don't take transforms into account' issue * Update ReleaseNotes.md.
github-actions bot
pushed a commit
that referenced
this issue
Oct 17, 2021
…essTemplates CONTRIBUTING.md Generators Nuget README.md Samples Source Tests doc docfx.json index.md license.txt Add test. BuildProcessTemplates CONTRIBUTING.md Generators Nuget README.md Samples Source Tests doc docfx.json index.md license.txt Fixes #830 'Bounds for SvgPath don't take transforms into account' issue BuildProcessTemplates CONTRIBUTING.md Generators Nuget README.md Samples Source Tests doc docfx.json index.md license.txt Update ReleaseNotes.md.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
PR #282 (Issue #281) introduced the logic for applying transforms to
SvgPathBasedElement
s. SinceSvgPath
overrides theBounds
getter and simply returnsthis.Path(null).GetBounds()
it bypasses possible transforms. Is this intended?If it is not I would propose simply removing the getter for
SvgPath
and fall back to theSvgPathBasedElement
's one. I could create a PR accordingly...The text was updated successfully, but these errors were encountered: