feat: calculate polyline visibility based on strokeWidth#2184
Open
braindamagedman wants to merge 3 commits intofleaflet:masterfrom
Open
feat: calculate polyline visibility based on strokeWidth#2184braindamagedman wants to merge 3 commits intofleaflet:masterfrom
strokeWidth#2184braindamagedman wants to merge 3 commits intofleaflet:masterfrom
Conversation
Member
|
Thanks for submitting this! We'll try to take a look at it as soon as we can :) |
Author
|
I fixed the formatting, but I’m not sure how to deal with the scoring issues. |
JaffaKetchup
changed the title
strokeWidth
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For thick polylines, setting
cullingMargin: nullis not always sufficient: if all polyline points are outside the viewport, the polyline is not rendered. This can be undesirable in many cases.