-
Notifications
You must be signed in to change notification settings - Fork 313
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
Swipe down to reveal steps list #1150
Conversation
# Conflicts: # MapboxNavigation/NavigationMapView.swift
@vincethecoder how shall we proceed here? Per voice yesterday, we discussed this probably is not the best user interaction since it's pretty hidden. |
@bsudekum Yes, ideally it makes sense to repeat the instructions when the user taps the |
…Added preview instructions button and action outlet to respond when button is tapped.
This might not be discoverable/tappable enough for something as crucial as getting the list of steps. Can we nest the button in the banner somehow? |
Per conversation today in chat, we came to the conclusion that we should change this to:
|
# Conflicts: # MapboxNavigation/RouteMapViewController.swift
As referenced from the ongoing conversation on slack channel, we came to a final conclusion today.
Issue reference: #1138 (comment) |
I'm getting a crash, to reproduce:
This value is set here: mapbox-navigation-ios/MapboxNavigation/RouteVoiceController.swift Lines 208 to 210 in 0c0a769
And is nil because the system is muted. |
@bsudekum cannot reproduce. Can you share the specific route, so that I can simulate it on my branch build? Thanks. |
@vincethecoder I do not think this is specific to a route. The issue is that |
@bsudekum Sure. I just wanted to test the referenced crash after the change was made. It didn't crash for me. I understand why this not setting the |
@bsudekum moreover, I don't believe the root cause of the identified issue will be in that function scope. We need to investigate why the notification's |
It's set to nil because the this check to mapbox-navigation-ios/MapboxNavigation/RouteVoiceController.swift Lines 208 to 210 in 0c0a769
|
…e state of the voice muted.
displayPreviewInstructions() | ||
} | ||
|
||
private func repeatInstructions() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Per #1138 (comment), we discussed that the first two steps would be implemented first. No need to do anything around repeating the instruction yet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bsudekum done ✅. This private function will just live here till we are ready to plug it in a delegate or gesture recognizer
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vincethecoder I think we should remove it and add it when it's time to add this feature.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok
…fied qualifiers of InstructionsBannerViewDelegate to optional objc delegate methods.
routeProgress = notification.userInfo![RouteControllerNotificationUserInfoKey.routeProgressKey] as? RouteProgress | ||
assert(routeProgress != nil, "routeProgress should not be nil.") | ||
|
||
guard !NavigationSettings.shared.voiceMuted else { return } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this can be undone.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bsudekum is there a reason why we have to undo this?
Let's break this PR up into two PRs:
|
@@ -56,6 +56,8 @@ extension BaseInstructionsBannerView { | |||
self.separatorView = separatorView | |||
|
|||
addTarget(self, action: #selector(BaseInstructionsBannerView.tappedInstructionsBanner(_:)), for: .touchUpInside) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests are failing because this function still exists but was removed here: https://github.com/mapbox/mapbox-navigation-ios/pull/1150/files#diff-7bae0cf60f54997d0d5e86fe02b5cddbL60 and renamed to draggedInstructionsBanner
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Resolved ✅
Scratch that, my pull didn't grab everything. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Per conversation, we're going to add the indicator button view in a followup PR.
@vincethecoder the changelog addition can go under the |
Added functionality to announce current navigation instructions when user puck is tapped.
Issue addressed: #979
PS: Ongoing discussion on what should respond to user interaction with map interface.
cc @mapbox/navigation-ios
TODO: