[Pronkle]

Description

Made navigation transition logic strictly dependent on user GPS location, events triggered based on leaving or entering a radius for things like stops, etc. Bus arrival UI in navigation is now live, walking directions are also live, and missed bus prompt is adjusted based on when the user leaves a bus stop.

Type of Change

• New feature (feat)
• Bug fix (fix)
• Refactor / code improvement
• Dependency / build update
• Documentation
• Other (explain)

Changed Files

(Please list all files you changed, each with a description of what you changed and why.)
Tip: see a list of everything you changed on the "Files changed" tab

Example:

• navigation_manager.dart
  • All logic handling stage transitions and prompting for the missedbus is here, along with live information feeding the header, the dot in the progress bar
• navigation_overlay_widget.dart
  • new ui implementations including the integrated missed bus dialogue primarily, replaced hard coded "bb mere moments" card with the live data one, progress bar fix as well
• time.dart
  • navigation eta text is for live eta and arrival prediction time, upcoming bus text is for the upper bus card (the formerly mere moments card)
• map_screen.dart
  • Changes made that logo and settings are hidden during nav, plus starting and stopping the navigation, so will catch if you can't start navigation, and also ensures gps polling ends once user quits navigation
• floating_draggable_sheet.dart
  • Changes made in order to accommodate the new missed bus design
• geometry.dart
  • Apparently some calculations were broken so these were fixed (some matrix calculations)

Related Issues

Closes #99 #108

Does your code rely on another PR

#134 #136
Need to make sure that the new journey polylines work ok across the board.

Testing Done

Flutter:

• Tested on:
  • iOS Simulator
  • Android Emulator
  • Physical device

Screenshots / Demo (if UI or notification change)

Checklist

• Commit messages follow Conventional Commits
• PR title follows [type](scope): short description
• PR target branch is not main and is our current working update branch (e.g. maizebus2.1)
• No print() / debugPrint() / console.log() left in production code
• Secrets / keys not committed

[Pronkle]

There are still some minor UI changes that need to be done before this is done and done, mainly that the buttons need to get changed a bit, and also some more broad things like text color.

The weird polyline issue for the journey should be covered by Edward's PR's for journey.

Main note though, we need to do some real world testing on real phones, I have not been able to since I have an iPhone.