The bug report of this weekend

Stephan shared this problem ago

Not a Problem

Track navigation: Automatic recalculation starts but I had to wait very often some minutes to get a result. Manual recalculation generates a result at once.

If I am not at the beginning of a track, starting the track navigation from the track menu cause no recalculation to a useful entrance to the track like in former versions of Locus Map.

Version 3.38.6

The same problem 0

Replies (2)

Stephan ●

Same problem is reported in

https://forum.locusmap.eu/index.php?topic=6622.msg56061#msg56061

https://forum.locusmap.eu/index.php?topic=6622.msg56063#msg56063

URL

Michal Stupka ●

Hi Stephan,

we've been testing latest version and navigation thoroughly over last days and we didn't notice anything like what you describe. What distance do you have set for auto-recaculation? Isn't it too far from the original route?

The second problem - use auto-recalculation with route priority.

Michal

URL

Stephan ●

"we've been testing latest version and navigation thoroughly over last days and we didn't notice anything like what you describe."

That you find nothing does not matter, if two other people have the same problems(see the post above). The difference is probably that we used the app you only tested the app.

URL

Michal Stupka ●

I'm sure the only way how to test the app is to use it. I'm sorry, Stephan, I can't help. If you think the newest version of Locus Map is worse than the older ones, you may want to downgrade. Here you can find older versions of Locus Map: https://docs.locusmap.eu/doku.php?id=manual:faq:devices_older_android.

URL

Stephan ●

Sorry Michael, this is a stupid answer.

I gave you two links, where two different people report the same issue. It is very easy for me to reproduce the problem.

https://drive.google.com/open?id=11E1ch9gwRxH2bdAVKkdxm-wCfljCHu7M

https://drive.google.com/open?id=11Cg_AjO8VxrGe_oBO8otKkShgYB6xQVb

https://drive.google.com/open?id=11ClEQc12iZMrvAZ8FwoMCVeh4wc6RFvv

That is the proof that there is a change in the code.

If it is a intentional change, you have to know about the change because it must be documented.

If it is a accidental change, than you have to search the change. If you are helpless and overwhelmed by this task ( or perhaps too lazy) you should not declare the issue, that this is not a problem.

Because this change cause a recalculation loop and one have to restart the programm or have to wait a long time.

If you think this is not a problem, you should not work in a customer support. You should not only have a brain, you should use it.

URL