You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 16, 2022. It is now read-only.
If paths store their extents on creation, then there is enough information to know whether a given geometry will be in view on compile. Re-computing the slab geometry with occlusion, while faster than computing without, may be slower than just reading the cache and letting viewBox handle the rest, though. Some testing required.
Maybe paths should cache themselves, not just slabs? Then it would just be a choice between reading in the cache or not.
The text was updated successfully, but these errors were encountered:
If paths store their extents on creation, then there is enough information to know whether a given geometry will be in view on compile. Re-computing the slab geometry with occlusion, while faster than computing without, may be slower than just reading the cache and letting viewBox handle the rest, though. Some testing required.
Maybe paths should cache themselves, not just slabs? Then it would just be a choice between reading in the cache or not.
The text was updated successfully, but these errors were encountered: