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
1ec5 opened this issue
Aug 5, 2020
· 0 comments
· Fixed by #2581
Assignees
Labels
bugSomething isn’t workingCarPlayBugs, improvements and feature requests on Apple CarPlayop-exRefactoring, Tech Debt or any other operational excellence work.
NavigationMapView.routeLineTracksTraversal is billed as an option to enable the “erasing route line” or “vanishing route line” feature on any NavigationMapView (#1307). But this property only works when the map view is embedded inside a NavigationViewController, because the only thing that reads the property is in RouteMapViewController. Nor does the feature work in CarPlay, which has a CarPlayNavigationViewController instead of a NavigationViewController.
Unusually, NavigationMapView.fadeRoute(_:) is an internal method not exposed publicly, so there’s no workaround for an application that implements its own custom UI for turn-by-turn navigation.
We should rename fadeRoute(_:) to updateRoute(for:), have it take a RouteProgress instead of a raw number, and expose it publicly. Since routeLineTracksTraversal is dependent on functionality outside of NavigationMapView, namely progress updates, we should either move it to NavigationViewController or move that conditional inside updateRoute(for:). Finally, we should call updateRoute(for:) from within CarPlayNavigationViewController.progressDidChange(_:) too.
The text was updated successfully, but these errors were encountered:
1ec5
added
bug
Something isn’t working
op-ex
Refactoring, Tech Debt or any other operational excellence work.
CarPlay
Bugs, improvements and feature requests on Apple CarPlay
labels
Aug 5, 2020
bugSomething isn’t workingCarPlayBugs, improvements and feature requests on Apple CarPlayop-exRefactoring, Tech Debt or any other operational excellence work.
NavigationMapView.routeLineTracksTraversal
is billed as an option to enable the “erasing route line” or “vanishing route line” feature on any NavigationMapView (#1307). But this property only works when the map view is embedded inside a NavigationViewController, because the only thing that reads the property is in RouteMapViewController. Nor does the feature work in CarPlay, which has a CarPlayNavigationViewController instead of a NavigationViewController.mapbox-navigation-ios/MapboxNavigation/RouteMapViewController.swift
Lines 460 to 462 in aaed03d
Unusually,
NavigationMapView.fadeRoute(_:)
is an internal method not exposed publicly, so there’s no workaround for an application that implements its own custom UI for turn-by-turn navigation.mapbox-navigation-ios/MapboxNavigation/NavigationMapView.swift
Line 603 in aaed03d
We should rename
fadeRoute(_:)
toupdateRoute(for:)
, have it take a RouteProgress instead of a raw number, and expose it publicly. SincerouteLineTracksTraversal
is dependent on functionality outside of NavigationMapView, namely progress updates, we should either move it to NavigationViewController or move that conditional insideupdateRoute(for:)
. Finally, we should callupdateRoute(for:)
from withinCarPlayNavigationViewController.progressDidChange(_:)
too./cc @mapbox/navigation-ios @d-prukop @avi-c @captainbarbosa
The text was updated successfully, but these errors were encountered: