Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Different maxBoundsViscosity for x and y axes
See original GitHub issueWould a PR for two additional map options maxBoundsViscosityX and maxBoundsViscosityY that both default to maxBoundsViscosity, if not explicitly set, be accepted?
If x and y are frowned upon, we could also go with maxBoundsViscosityLng and maxBoundsViscosityLat.
In our case, we want to restrict panning to one axis only, but keep the bounciness when reaching the end. Currently this is not possible without also allowing a bit of viscous panning on the other axis.
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yeah, that’s buried somewhere in the “extending Leaflet” tutorials 😄
I’ll wait for your plugin then 😉
Don’t unregister it. Replace the behaviour of
L.Map.DragwithL.Map.Drag.include({...});.