Discovery scan summary map: the scanner plus everything it heard.
Same treatment as the traceroute map, and for the same reason: satellite imagery is often the useful backdrop for asking why one node was heard and another was not, and until now this map could not show it.
Discovery scan summary map: the scanner plus everything it heard.
Same treatment as the traceroute map, and for the same reason: satellite imagery is often the useful backdrop for asking why one node was heard and another was not, and until now this map could not show it.
Single-node mini-map embedded in the node detail sheet.
Follows the basemap preference, so it matches the map the user was just looking at.
Single-node mini-map embedded in the node detail sheet.
Follows the basemap preference, so it matches the map the user was just looking at.
MapLibre implementation of MapViewProvider, shared by the F-Droid flavor and the desktop app.
Not a Koin @Single: the two call sites construct it directly, which keeps this module free of any assumption about how the host app wires its graph.
MapLibre implementation of MapViewProvider, shared by the F-Droid flavor and the desktop app.
Not a Koin @Single: the two call sites construct it directly, which keeps this module free of any assumption about how the host app wires its graph.
Traceroute result map: forward and return paths plus the hops they pass through.
The Google flavor reaches this through its main map composable, so it arrives with the toolbar and the basemap already chosen. Here it is its own composable and has to ask for both. No filter: a traceroute is the route it is, and there is nothing on it the main map's filters apply to.
Traceroute result map: forward and return paths plus the hops they pass through.
The Google flavor reaches this through its main map composable, so it arrives with the toolbar and the basemap already chosen. Here it is its own composable and has to ask for both. No filter: a traceroute is the route it is, and there is nothing on it the main map's filters apply to.
The mesh map, rendered by MapLibre.
Presents mapState and nothing else; what gets drawn is declared by rememberMeshMapState.
basemap must be the same one that state was built with: it supplies the zoom range the camera is held to, and a different value here would clamp the camera to a range the loaded style cannot serve.
The mesh map, rendered by MapLibre.
Presents mapState and nothing else; what gets drawn is declared by rememberMeshMapState.
basemap must be the same one that state was built with: it supplies the zoom range the camera is held to, and a different value here would clamp the camera to a range the loaded style cannot serve.
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.
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.