Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Always send progress update except when location is unqualified #1126

Merged
merged 1 commit into from
Feb 16, 2018

Conversation

bsudekum
Copy link
Contributor

This removes the notification key MBRouteControllerEstimatedTimeUntilManeuverKey in favor of using durationRemaining on currentStepProgress, and makes sure progress updates are always fired when the location is deemed qualified.

When a user begins to go off route near a maneuver, this check if distanceTraveled != currentStepProgress.distanceTraveled { would fail because the distance traveled is a snapped distance. Although the distance is not changing, we still need to emit progress updates. This was not surfaced because we're updating the user puck via this delegate method instead of progress update notifications. This is important for developers who are implementing custom UIs.

/cc @mapbox/navigation-ios

Copy link
Contributor

@JThramer JThramer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@bsudekum bsudekum merged commit 2483d16 into master Feb 16, 2018
@bsudekum bsudekum deleted the always-send branch February 16, 2018 22:10
@1ec5 1ec5 added the backwards incompatible changes that break backwards compatibility of public API label Dec 18, 2018
@1ec5 1ec5 added this to the v0.14.0 milestone Dec 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backwards incompatible changes that break backwards compatibility of public API
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants