UI Maps/com.mapbox.navigation.ui.maps.route.callout.api

Package-level declarations

Types

Link copied to clipboard
class DefaultRouteCalloutAdapter(context: Context, options: DefaultRouteCalloutAdapterOptions = DefaultRouteCalloutAdapterOptions.Builder() .build(), routeCalloutClickListener: (DefaultRouteCalloutAdapter.CalloutClickData) -> Unit? = null) : MapboxRouteCalloutAdapter

Default implementation of MapboxRouteCalloutAdapter that introduce two types of callout representation:

Link copied to clipboard
abstract class MapboxRouteCalloutAdapter

Adapters provide a binding from an app-specific data set to callout views that are attached to each route line.

Link copied to clipboard
class RouteCalloutUiState

Represents UI data required to attach a DVA with this callout for a specified route. See RouteCalloutUiStateData for more details and supported use cases.

Link copied to clipboard
class RouteCalloutUiStateData

UI state for route callout. Normally, route callouts are drawn under the hood in NavSDK when this feature is enabled in com.mapbox.navigation.ui.maps.route.line.model.MapboxRouteLineApiOptions. However, there might be cases when app wants to only get the callout data from NavSDK and attach the DVA itself. An example of such a case is using Mapbox Maps SDK Compose extensions: attaching a DVA for Compose MapboxMap is done via compose-specific API, which is not currently supported by NavSDK. In this case you may listen to RouteCalloutUiStateData updates and use its information by attach a DVA. See RouteCalloutUiStateProvider for details on how to subscribe.

Link copied to clipboard
class RouteCalloutUiStateProvider

Provider of UI state for route callouts.

Link copied to clipboard