read https://www.locusmap.app/heres-all-you-asked-us-during-the-last-two-weeks/ for more info on the upcoming enhancements to LoRouter
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: lor74cas on April 20, 2021, 08:03:45@lor74cas I disagree on this aspect - although I doubt I'd use it much, I don't see that as a reason to remove it. In my limited desktop testing the results were interesting and within expectations.
ROUND TRIP:
Unless real utility can be found for this feature, integrating it with the options I wrote above (and all the complications of the case), it should be removed, useful and solid functionality better than things like this that do nothing but generate doubts in users.
Quote from: Viajero Perdido on April 18, 2021, 01:41:43@Viajero Perdido - thanks so much - finally after a year I understand how this feature works - I had asked Menion a year+ ago when feature first implemented but never understood why it always failed.
I had the same confusion, with nothing more than an error message to guide me. I assumed (like others?) that you use that function after you've drawn the route to your destination, then it [does something magical] to get you back.
No, that's not the intent, you eventually figure out. May I propose, "Suggest round trip"?
Quote from: slarti76 on April 17, 2021, 15:30:27the Cloud Sync doco should be improved (written) asap so users like in this topic https://forum.locusmap.eu/index.php?topic=7334.msg63206#msg63206 & https://help.locusmap.eu/topic/24280-cant-save-a-planned-route-to-library-on-web-planner don't get confused/ better understand how it operates/ don't have an unnecessary bad experience/ don't loose data or have duplicated data ==> give undeserved reviews. Bad ratings don't help anyone.
Well, played around with the syncing, back and forth, Route Planner, Track Editor - couldn't find any wrong behaviour whatsoever!
Quote from: Menion on April 17, 2021, 06:40:07@menion - thanks for reply, but now I am more confused - how can a route be generated (completed) if there is only 0 or 1 points in existing route? My route example had 2 points so far. I am just curious/ testing as I have no real use-case, but if the function is there it should be more intuitive so reduce the Locus team support load.
Problem is that you have more than one point on the map. Reduce it to 0 or 1 and it will work.
Quote from: Menion on April 17, 2021, 06:40:07ahh - GraphHopper - ok, But now BRouter/ LoRouter is the default navigation source, lots of users will have the same confusion & question. I wait in hope. Should I start a help topic for voting?
Street names, if I remember correctly, they are visible when computed over GraphHopper
Quote from: Menion on April 15, 2021, 10:38:06nice
crash info is stored in the app and send when app starts next time.
Quote from: Menion on April 15, 2021, 10:38:06yes/ no worries/ my report was just in case you weren't already aware
Swiping point/track panel > you mean on the tablets where is attached to the right side right?
Quote from: Menion on April 14, 2021, 15:44:42@Menion - nice system - does Locus device need to have Wifi or mobile data enabled at the precise time of any crash or the crash data cached then possible to upload later when comms are available?
New Beta version 4.0.2.2 just uploaded to Google Drive.
I test automatic reports of crashes to "bugsnag" service
Quote from: Menion on April 10, 2021, 11:58:23@Menion - damn me too - didn't see your suggestion in time - I uninstalled 4.0.2 & reinstalled 4.0.1.1. Oh well. 4.0.2.1 - fixed - thanks.
Beta version
damn, this is really complicated task now . Andrew, I probably see your crash in auto reporting system. Seems two users already have this problem. Reason? You probably set the bottom panel to full auto-hide and 4.0.2 does not know this option = crash .
id: 15eb32dd-3c20-455f-acec-6eb953c42ef8
status: 10600
start: 11 Apr., 09:19
end: 11 Apr., 09:19
changesSince: 1 Jan., 11:00
plan:
operation POINT_GROUP, pull: 0, pullDelete: 35, push: 0, pushDelete: 0
operation TRACK_GROUP, pull: 0, pullDelete: 23, push: 0, pushDelete: 0
operation POINT, pull: 0, pullDelete: 332, push: 0, pushDelete: 0
operation TRACK, pull: 5, pullDelete: 126, push: 0, pushDelete: 0