[Regression] Route status not set correctly when simulating a route

Bug #1571596 reported by Nekhelesh Ramananthan
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
uNav
Fix Released
Critical
costales

Bug Description

I have noticed a regression with the route status. This is reproducible in trunk and the store version. So it was not newly introduced in this development cycle.

Steps to reproduce bug:

First add the following line of code, onRouteStateChanged: console.log("Route Status: " + routeState) to the mainPageStack in Main.qml file.

1. Press Simulate Route and choose Point A
2. Now choose Point B

Notice the following output of routeState in the log files,

qml: Route Status: simulate_calculating
qml: Route Status: no

As you can see it sets the route status to "no", which is incorrect! Now open any page like the Settings Page or the route page and then return to the map by pressing the back button. At this point, notice the output,

qml: Route Status: simulate_done_bike

The reason this bug is critical is because, the first time you open the route page after simulating a route, you don't see a "Cancel simulation" button since the route state is "no". Only when you open the route page a second time, you see the "Cancel button".

This bug is even more serious in the new menu navigation strucuture since the so called "destination header action" is not visible when you simulate a route.

Related branches

costales (costales)
Changed in unav:
status: Triaged → In Progress
Changed in unav:
status: In Progress → Fix Committed
Changed in unav:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.