... the user friendly GPS tool


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
re-routing refresh
#1
I had this issue for sometime now but lately its becoming an annoyance. 

When trying to modify a route created previously by adding new waypoints or changing waypoint position Routeconverter will calculate the new routing but most of the times will still display the old bit of route ie the screen will not refresh with the new route only. 

Only way to resolve this is to close RC and reopen it. 

Any ideas how to resolve this?

Many Thanks
Reply
#2
(18.09.2020, 15:56)Stav Wrote: Any ideas how to resolve this?

I've tried this several times – somehow the state of the mapsforge-Library and RouteConverter about which objects are actually visible on the map diverges. I do know that it's related to the use of multiple threads to speed up the rendering. I have a test case to reproduce but couldn't find and understand the problem yet.

And in case you might think "why not disable the multiple threads?" – then RouteConverter becomes unusable above 10 or 15 waypoints.

Maybe it helps, if you'd compile a tiny test sequence that shows the problem?
--
Christian
Reply
#3
Hi Christian,

I put together a short route with 3 waypoints. As you can see from the video a new route is created by adding / moving / deleting a waypoint but the old route remains. You can see it clearly by changing the colour of the route - the old routes remain with the previous colour.

Reopening the route or loading a new route still displays the old route.

v2.28 and win10. Please note I get the same behaviour on different laptops

Quality of the video below is not great but a better quality from this link
https://mega.nz/file/GJtSxDIC#N2Uk3zOSo1...Ve_F0mH11U

Hope this is of help.

Reply
#4
I've found a race condition between the update of the route due to an insertion of a new waypoint and the asynchronous process, that adds meta data like location name, elevation etc.

To address (I don't say fix) this, I've introduced some harsh synchronisation mechanisms. This might lead to performance problems.

Please test the prerelease which I've just uploaded and report any problems and issues.
--
Christian
Reply
#5
So far it looks good.
Haven't noticed any performance issues yet but will be playing with a track with a few thousand points later on. Let you know...

Sorry for the delay but I do not get notifications of posts
Reply
#6
Hi,
Playing with a track I recorded at my last ride of around 5500 waypoints. I reduced down to 70 with a lot of adding and moving waypoints around.
Screen route was refreshing with no problems and no old routes left showing.

I havent noticed any performance issues at any time.

One think I noticed, but if not mistaken I think I noticed at previous versions, is the length calculation. It seems to almost double the length.

A route I imported and after modifying it shows Route=248 miles and Track=118 miles
Shutting and restarting RC and reloading file shows the correct lenght, 135 miles
Reply
#7
(06.10.2020, 15:10)Stav Wrote: Haven't noticed any performance issues yet but will be playing with a track with a few thousand points later on. Let you know...

I found, that the change makes RouteConverter unresponsive during the download phase.

(06.10.2020, 15:10)Stav Wrote: One think I noticed, but if not mistaken I think I noticed at previous versions, is the length calculation. It seems to almost double the length.

A route I imported and after modifying it shows Route=248 miles and Track=118 miles
Shutting and restarting RC and reloading file shows the correct lenght, 135 miles

I've tried to replicate that observation but failed. Do you have an example?
--
Christian
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)