Add new maxBoundsResistance option #2224
Closed
Conversation
This file contains 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
|
Nice idea! Thanks for the pull, I'll take a look. I was thinking of doing something similar, but need to check if it affects performance in any way (as drag happens often, so we should avoid lots of ops in predrag handlers if possible). |
|
Covered by #3510 |
29 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Obey maxBounds during dragging a map.
New option "maxBoundsResistance" (0.0 - 1.0) controls its behavior;
0.0: Classic (No effect during dragging)
0.8: Modern reaction
1.0: Strictly forbid to beyond the maxBounds