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 was archived by the owner on Aug 8, 2023. It is now read-only.
The Android SDK should use animators to drive camera transitions in response to gestures and calls to methods like animateTo(). We should move off mbgl::AnimationOptions and use the mbgl::Transform methods only for incremental transform changes on each frame of the animation.
A key benefit is that the Android SDK will be able to implement concurrent animations (#3625) without us having to design an API around tweening, spring solving, or the like.
@tobrun started doing this as part of #8031. Perhaps there’s also prior art in the Qt SDK, where we’ve always relied on Qt animation APIs instead of mbgl’s.
The Android SDK should use animators to drive camera transitions in response to gestures and calls to methods like
animateTo(). We should move offmbgl::AnimationOptionsand use thembgl::Transformmethods only for incremental transform changes on each frame of the animation.A key benefit is that the Android SDK will be able to implement concurrent animations (#3625) without us having to design an API around tweening, spring solving, or the like.
@tobrun started doing this as part of #8031. Perhaps there’s also prior art in the Qt SDK, where we’ve always relied on Qt animation APIs instead of mbgl’s.
/cc @zugaldia @ivovandongen @bsudekum