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
found the culprit - it's my update_view functions & logic.
For some reason the viewState is not keeping a reference to the auto-calcualted "location" in the first add_path(), so on the button presses it's not being set at the correct location, and requires interacting with the map to force a re-draw (or using update_view = TRUE in the subsequent add_path() calls
Time for a re-think...
It seems to be the solution is a recommendation:
If you'll be adding & removing layers dynamically and want to use update_view = FALSE each udpate, don't supply data to the original mapdeck() call
This happens when you've initialised the map with data, then use an
observeEvent()
to change it.(and it's almost replicating the behaviour we sometimes see where the layer is 'sticky'. Maybe they're related?)
The text was updated successfully, but these errors were encountered: