feature-map-maplibre/org.meshtastic.feature.map.maplibre/rememberMeshMapState

rememberMeshMapState

fun rememberMeshMapState(viewModel: BaseMapViewModel, navigateToNodeDetails: (Int) -> Unit, basemap: Basemap = Basemaps.default, initialCameraPosition: CameraPosition = CameraPosition(), overlays: List<MapOverlay> = emptyList(), layerOpacity: Map<String, Float> = emptyMap(), customLayers: List<CustomLayer> = emptyList(), onClusterMembers: (List<ClusterMember>) -> Unit = {}, onWaypointClick: (Int) -> Unit = {}, boxCorner: Position? = null, locationState: LocationState? = null, followLocation: Boolean = false, bearingUpdate: BearingUpdate = BearingUpdate.IGNORE, frameOnNodes: Boolean = true): MapState(source)

Everything the mesh map draws, as one MapState.

Since maplibre-compose 0.16.0 the base style and the sources and layers over it belong to the state rather than to a trailing block on MaplibreMap, so this is where the mesh data is read and turned into layers. MeshMap presents the result. The state is returned because the caller also needs it: the toolbar reads the bearing off it, the zoom buttons move it, and the Site Planner asks it where the map is pointed.

The camera effects stay out of the style block, even though that is where upstream puts LocationTrackingEffect. The library hosts style content in a subcomposition keyed on the loaded style and disposes it on every base-style switch, so a remember in there does not survive the user changing basemap.

Shared by the F-Droid Android flavor and the desktop app — the two differ only in what they hand in, not in what gets drawn.