addDataSetWithCachingScope
Adds a new MPDataSetCache
Return
Added MPDataSetCache if added - If a MPDataSetCache with the same solutionId is already found, we return that.
Parameters
- SolutionId for the dataset
- MPDataSetCacheScope scope to cache
Adds a new MPDataSetCache with base-map tile caching enabled or disabled from the start, saving a follow-up call to setBaseMapTilesEnabled
Scoped to every venue in the solution. See addDataSetWithCachingScope for what the flag does and for how an already-managed solution is treated.
Return
Added MPDataSetCache if added - If a MPDataSetCache with the same solutionId is already found, we return that.
Parameters
- SolutionId for the dataset
- MPDataSetCacheScope scope to cache
- true to also cache the map provider's base-map tiles for this dataset
Adds a new MPDataSetCache with base-map tile caching enabled or disabled from the start, saving a follow-up call to setBaseMapTilesEnabled
The flag only marks the dataset, it downloads nothing — call synchronizeBaseMapTiles for that. It is orthogonal to cachingScope, so any combination is legal.
Note that, as with the other overloads, an already-managed solution is returned unchanged: baseMapTilesEnabled is then ignored, exactly as venueIds and cachingScope already are. Use setBaseMapTilesEnabled to change the flag on a dataset that is already managed.
Return
Added MPDataSetCache if added - If a MPDataSetCache with the same solutionId is already found, we return that.
Parameters
- SolutionId for the dataset
- Ids of the venues to scope the dataset to, or null to scope it to every venue
- MPDataSetCacheScope scope to cache
- true to also cache the map provider's base-map tiles for this dataset