This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
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.
Whilst
Transform::easeTo
interpolates the zoom from initial to end values (thus never breaching the end value threshold),Transform::flyTo
has a "bounce" effect on zoom in some circumstances, by applying a formula on each frame rendering that calculates a new zoom value.In a particular case e.g. executing
flyTo
with camera options' zoom level set to the maximum value, the zoom value sometimes goes above the maximum zoom threshold, causing the transform state to become invalid, thus causing this crash intileCover
:This PR introduces a clamping to scale boundaries in
TransformState::setLatLngZoom
, and also a check if the frameZoom is NaN inflyTo
(which can occur if the transform state size is empty).