Opened 15 years ago

Closed 13 years ago

#124 closed defect/bug (fixed)

refresh the route when recalculated

Reported by: kiddo Owned by: KaZeR
Priority: major Milestone: version 0.2.0
Component: core Version:
Severity: Keywords: usability


navit can recalculate routes automatically, but the display does not reflect the changes at all. You have to move the map or hit Refresh to know that the route has changed.

Navit should refresh the route when it is recalculated.

Change History (6)

comment:1 Changed 15 years ago by KaZeR

  • Milestone set to version 0.1.0
  • Owner changed from somebody to KaZeR
  • Status changed from new to assigned

Currently, Navit refresh upon two criteria : new position from gps, and user has forced follow=1, or the cursor hits a border of the screen. But your suggestion makes sense to me.

comment:2 Changed 15 years ago by kiddo

but currently, it does not refresh when the gps position is updated. At least not on my side. The gps position cursor moves, but the route "behind" it does not clear itself up. Are you sure it works? ;)

comment:3 Changed 14 years ago by kiddo

ah indeed it works with follow=1, I did not understand what you meant initially. That option is not so easily discoverable though.

comment:4 Changed 14 years ago by KaZeR

  • Milestone changed from version 0.1.0 to version 0.0.5

We could force a refresh if the route has been recalculated.

comment:5 Changed 14 years ago by KaZeR

  • Milestone changed from version 0.0.5 to version 0.2.0

comment:6 Changed 13 years ago by akashihi

  • Resolution set to fixed
  • Status changed from assigned to closed

According to the following code:

if (this_->route) {

struct attr callback; this_->route_cb=callback_new_attr_1(callback_cast(navit_redraw_route), attr_route_status, this_); callback.type=attr_callback; callback.u.callback=this_->route_cb; route_add_attr(this_->route, &callback);


It appears to me, that the route refresh is called, when route_status is changed and route_status is changed during route recalculation. So it looks fixed :)

Note: See TracTickets for help on using tickets.