-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Trying out 6.0.0: fade in animation on symbols #10916
Comments
Thank you for reaching out. The fix for this was merged 17 hours ago here. You can retest this with the latest 6.0.0-SNAPSHOT build. |
I was able to reproduce the issue on The example code:
/cc @ansis @ChrisLoer |
With global/viewport collision detection (PR #10436), the fade-in for new symbols is currently unavoidable for symbol layers that require collision detection. If you don't need collision detection, you can disable it for that layer with Your example of updating an existing symbol is triggering a fade-in/fade-out because the symbol is "moving" to a new layer (from the point of view of all the symbol code, that basically makes it a completely new symbol). It's possible for us to add functionality for controlling the fade duration of collision animations, but we don't have a good way to distinguish "just added" from "just stopped colliding", so if you shortened/eliminated the fade animation it would affect both. |
Also wanted to add that a solution for the above use-case would be using a single source which refreshes both layers at the same time, for example:
Closing as not actionable/resolved. |
Platform: Android
Mapbox SDK version: 6.0.0 (snapshot)
Steps to trigger behavior
Expected behavior
The symbol should be shown immediately (same behavior seen in pre 6.0.0)
Actual behavior
The symbol is appearing progressively (fade-in effect)
I'm not sure if it's a feature (if so, can it be disabled?) or a bug?
The text was updated successfully, but these errors were encountered: