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 has been archived by the owner on Sep 5, 2024. It is now read-only.
There is increasing need to call a specific base map within a plugin, and even be able to switch base maps based on in-plugin functionality. This would override the framework base map. Here are the latest Esri options for customization and configuration we would like to deploy. https://blogs.esri.com/esri/arcgis/2015/11/18/introducing-esri-vector-basemaps-beta/
The text was updated successfully, but these errors were encountered:
This could be done, though there are a few scenarios to consider:
The app could specify the default basemap that should be shown when it is activated, but that could result in a jarring effect when a user switches back and forth between apps
The app could offer a custom button or selector to change the basemap, which would then be persistent even the when app is closed. The issue here is that it may be confusing to have the same functionality in two spots (main map and an app) but then not in other apps.
The basemaps explicitly linked to in the issue are new vector tile based maps. I'm not sure how they're rendered on the client and we'll need to confirm that the version of the API supported by the framework can support them.
There is increasing need to call a specific base map within a plugin, and even be able to switch base maps based on in-plugin functionality. This would override the framework base map. Here are the latest Esri options for customization and configuration we would like to deploy. https://blogs.esri.com/esri/arcgis/2015/11/18/introducing-esri-vector-basemaps-beta/
The text was updated successfully, but these errors were encountered: