Show Posts

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.

Messages - menion

Pages: [1] 2 3 ... 720
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: Today at 09:34:44 »
@Žajdlík Josef
hmm, seems that Strava use exactly same old system that Locus Map used > so it computes directly from coordinates of current and next trackpoint. Not an ideal solution I think. I've reverted this part of the code to keep it as is anyway expect that I'll most probably change it in the future to the result very similar to current Beta, thanks (based on a floting average from previous & next trackpoint)

anything new compares to Pro version?
And too high ... heh ... you may check five other apps or web pages to find that every compute values differently. I believe that values in Locus Map should be somewhere in the middle ...
Also depends if you use Heart rate monitor or not ...

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 17, 2019, 15:34:29 »
hmm, it depends on what you clicked. If on the middle button, it says to Locus: "insert this point to the nearest place in planned route as possible". In your case, it is inserted into previous points 3 and 5. So you probably really get a route from 3 to 4 and almost back to 5.
Try to use the last third button to add cache to the route. This says "insert this point to the end of the planned route".

Here is exact content from BRouter that is send to Locus Map (just fresh downloaded routing data).

<wpt> has name "u-turn" and also rtePointAction: 13 indicate to Locus that navigation command is u-turn.

Code: [Select]
<?xml version="1.0" encoding="UTF-8"?>
<!-- track-length = 201 filtered ascend = 11 plain-ascend = 11 cost=610 -->
 creator="BRouter-1.4.11" version="1.1">
 <wpt lon="-3.903960" lat="52.388070"><ele>293.0</ele><name>u-turn</name><extensions><locus:rteDistance>110.0</locus:rteDistance><locus:rtePointAction>13</locus:rtePointAction></extensions></wpt>
   <trkpt lon="-3.903181" lat="52.388660"><ele>282.75</ele></trkpt>
   <trkpt lon="-3.903502" lat="52.388477"><ele>285.5</ele></trkpt>
   <trkpt lon="-3.903802" lat="52.388360"><ele>287.75</ele></trkpt>
   <trkpt lon="-3.903931" lat="52.388255"><ele>289.75</ele></trkpt>
   <trkpt lon="-3.903960" lat="52.388070"><ele>293.0</ele></trkpt>
   <trkpt lon="-3.903483" lat="52.388088"><ele>293.75</ele></trkpt>
   <trkpt lon="-3.903146" lat="52.388137"><ele>293.75</ele></trkpt>
   <trkpt lon="-3.902419" lat="52.388305"><ele>293.75</ele></trkpt>

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 16, 2019, 10:54:44 »
I had also Z1C ... it was the best phone I ever had. By my stupidity I broke it maybe a year ago, anyway it is my personal interest to keep Locus Map working on this device as long as possible ;).

really no need to sorry :).

The App doesn't know for which reason the route was left. For this I brought up the 2 recalculation idea.
First, Locus can assume it's just a simple missed navigation etc.
After this 2 recalcs the App should assume the route can't follow this way and should find another way which means it's fine to skip a part of the route.

This is partially implemented. After two "failed" recalculations (user ignored new route), app place temporary no-go place behind the user to force routing engine to compute forward and not backward. Anyway, this logic does not affect "target" where recalculation is done and this is what we talk about here.

I still do not see a simple solution. I perfectly understand your reasons anyway as you wrote: "The App doesn't know for which reason the route was left.". In this case (your route) it is almost circular route which complicates the situation. App has absolutely no idea if you are off route because you want to skip the whole circle or you just pick some detour because of complications on road. In rare cases when this happens, exists in the navigation menu button "Nearest point" that should fix this situation.
It is not automatic, which means it is not an ideal solution.

I'll keep thinking about it and collecting ideas. For now, I really think that changes from last weeks are quite big and this not-so-often use case may be solved in another iteration.

understand and thanks for screenshots.
Hope you got the point of these changes in app. If now, simply: app try to unite visibility of content of all maps. Compare vector maps and some online (raster) in Pro and in Beta. Mainly check visible texts. In Beta, there should be very similar in terms of size. On modern devices (with huge DPI), all raster maps are useless in LM Pro.

You, as well as almost all other users,  had to solve this by "Map resolution" option. This unfortunately scaled also vector maps = problem.

So generally, "Map resolution" should be no longer important settings. It may be left on default 100% except for cases, you had worst eyes and really need a larger map.

@Andrew Heard
no problem. I found an issue in pinch zoom when work with world map = fixed. On your screenshot was higher zoom so it won't be this issue, but I'll keep watching it carefully, thanks.

something close to what you want is planned. Anyway, some other priorities firstly :)

Perfekt!! To téma, to je klíč.

Na něco jsem přišel a myslím že v další verzi (možná už příští týden) to bude opravené. Pokud ne, dej prosím vědět a já se na to ještě podívám. Díky

[CZ&SK] - diskuze o Locusu / Re: Locus se minimalizuje
« on: May 16, 2019, 08:42:18 »
Hmm a to obnovení funguje tak, že je okamžitě během vteřiny vidět mapa a nebo to celé trošku trvá, nejspíše je i vidět ten načítací dialog a celé to zavání spíše tím, že Locus Map startuje komplet znovu?

Děje se to samé i pokud běží v Locusu nějaká služba jako záznam trasy, Live tracking, POI Alert, ...?

Troubles & Questions / Re: Problems with navigating a route
« on: May 16, 2019, 08:40:44 »
uff, both issue should be fixed, thanks. The whole system is quite sensitive on indexes, so I'm sure there will be a situation when the result won't be perfect. Step by step to victory :).
Thanks Willy!

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 15, 2019, 14:54:29 »
I remember I made some smaller changes here based on some discussion on the help desk, so yes, if there is the difference, it is intent. But the link to discussion is not stored in my memory, sorry :).

Anyway, the idea behind this was for sure fact, that result of export is a) not so important because automatic = "I do not want to care at that moment" and also the result is visible in notify centrum.

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 15, 2019, 14:27:26 »
Result of automatic export should be visible in the notify center in the top-right corner of the map. There is no need for extra floating notification.

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 15, 2019, 14:05:57 »
Interesting. I noticed and already fixed one problem like this in one previous version and since that, I never saw it again.
Does this happen only with vector maps? At least that zoom in/out fit it :)

@Žajdlík Josef
testing and seems that it works correctly. Are we talking about manual export from the detail of the track?

zkouším to s kolegy asi na pěti telefonech a všude nám to funguje korektně. Tohel by se mohlo dít snad jedině pokud by telefon posílal z add-onu do Locusu ikony v jiné než plně černé barvě. Vy máte standartní rom v telefonu nebo nějak modifikovanou (custom rom)?

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 14, 2019, 08:18:44 »
Fine, so major problem ... crash at the start ... seems to be solved, perfect.
zooming was always a problem. I'll look at it, thanks.

I'm thinking if there is really any problem.
What is the purpose of this your trip?
To ride along predefine route? In this case, Locus Map correctly tries to get you back on route, isn't it?
Or to ride to the destination? Then point-priority is needed.

Here is a general problem that you skipped quite a long route segment. Thanks for the GPX file, I'll try to play with it, but now sure I'll find any simple solution now  :-\.

well and how works current Locus Map Pro with this map? There should be a similar problem. Well right, in LM Pro, upscale of level 13 isn't so visible as is in Beta. Two missing levels may be a problem here.
At which scale app switch from 16 to 13 and opposite? It is mentioned 13/274%? And when you zoom out from 16 then it's 16/?%

if it's not a huge problem, leave it for now. There is a chance, it will work in the next version. Maybe you expect exact on-time backups but it does not work like this. There may be a really big time difference between planned and real backup.

I would like to finish the biggest problem and publish a new version next week and we may solve this later, ok? Thanks.

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 13, 2019, 17:20:57 »
Uff so seems good news, thanks guys.

What I have found and fixed since
  • sometimes not reliable "hold map center"
  • still visible LoPoints after switching from LoMap to different map (needs a better approach in future)
  • not working LoPoints attached to any other vector map (V4 OAM for example). Now it works as well.

Troubles & Questions / Re: Problems with navigating a route
« on: May 13, 2019, 12:53:47 »
Heh, same as in my answer 11 days ago on the help desk, I mix two cases, sorry :).

We talk here about recalculation, so I again wanted to say that for point-priority, via-points are must-pass.

Anyway, new version just published and it should solve
a) issue with via points & route-priority as in attach file (thanks for help)
b) added hopefully nice tool that should prevent recalculation back if user ignore "turn back" 2 times. So if you ride forward, app two times recalculate back and you still ride forward, 3rd recompute should be forward and not backward.

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 13, 2019, 12:50:54 »
Thanks Libor, email received.
In Locus Map is used a system called "crashlytics" that automatically sends these serious crashes to web console where I may see them. And I see exactly this problem that affects 11 Beta testers. But as I wrote ... no exact idea why this crazy error happens... which happens sometimes :).

I made some changes and the new version is in preparation.

"" > Locus Map Free
"" > Locus Map Pro

Pages: [1] 2 3 ... 720