Messages

Maybe add an advanced option which inverts  it? Default=eye symbol and temp. hide?

I was worried that someone will want this

I was half a day converting a few more "config.cfg" parameters to the UI and noticed, how many!!! tiny settings that use just a few users, exist. I'll really need to reduce this or at least not create many new ... thanks for understanding.

[new Beta 4.17.2.2 version]

Hi guys,
(most probably) final solution published in the new Beta 4.17.2.2 version. I got your point, but do not fully agree with all.

Main use-case, the clearest to basic users: unload points. So this will be the primary function of this button. After confirmation, the button is disabled and counter reset so I believe, it is clear what this function did.

The secondary function, by the long click, is the temporary hide of all points/tracks.

I believe this will be useful good enough, anyway let me know if ...

Hi guys
- counter for points/tracks fixed (there were issues with incorrect values)
- left area (icon) for a quick return to the map after you select a theme > done
- "Map overlays" are now hideable
- app remember the scroll of this panel > currently intent so you may easily continue where you left. Better starting always at the top without a scroll? Hmm..

[new Beta version]

Enjoy the weekend with the new version on Google Play & new published new Beta version (with an improved map content panel).

@jonny.blue
uff 

Yes, as Tapio wrote. This dashboard had to be part of some automation. So it is most probably defined in any "Preset", or was simply used last time and the app tries to load it again? Simple selection of different existing dashboard does not help?

Hmm good point ... app currently supports local "pdf" files and external "html" links. So if you have a theme named "my_theme.xml", than app automatically searches for "my_theme.pdf" legend file. I'll improve this to the next app version and add also support for "my_theme.html" file.

Embedded images has a huge advantage: the display of such file is a lot faster because there is only a single request to download the file. Also, it allows using a theme embedded into the zipped theme. If there will be HTML + images, the legend in the "zip" won't work.

[@Andrew Heard]

@Andrew Heard
can't imagine how this may be possible. Maybe you used theme extracted, not in zip form?

@Tapio
no problem. We use a small generator for this, anyway created final version of EN legend for LoMap is attached here. Not sure how may I help you more with it ...

[@Andrew Heard]

@Andrew Heard
- error when clicking a legend: issue in the theme. Legend is in this theme defined over "lnk" file it should contain the relative path to the XML file (as I wrote for example here).

I'm thinking if I should fix this on my side (rather not) so suggest to @karlchick to fix it in the theme.

@Tapio
hidden tracks + visible track waypoints > I would like to stay with the current solution, because waypoints are directly connected to the track!

@T-mo
agree that hide points/tracks need some tweaks. I'm currently changing it a little bit ...

Bug > ah, thanks, will be fixed.

Hello Lupin,
if you compute the route also with BRouter external app on the Android and the result is the same as with Locus Map itself, then it looks more like a problem of the BRouter.

It is anyway task to @Radim V who take care of this in our team. So Radim, any known problem?

Hmm wait, a visible error message is displayed only in the second case I wrote about before!!

It means that the system killed Locus Map app when running on the background so once you turned the screen on again, the app was restored but because of 10+ between kill & restore, the app automatically paused recording.

You have to exclude Locus Map from battery optimizations, "that's all".

Hello Thomas,
thanks for the shared backup. For unknown reasons, in the database exists two points that do not belong to any group. How this may happen > I have no idea. Anyway, it was solvable so it is improved in the new Beta version. If you have a moment, give it please a try, thanks.

[Beta version 4.17.1.3]

New Beta version with some fixed crashes etc. and mainly a new side map-content panel with hopefully useful improvements. Feedback is welcome of course, thanks.

Beta version 4.17.1.3, download.

Hello guys,
new Beta 4.17.1.3 just generated. I've found also one extra issue in consumption that may happen in the case, in the directory is really a lot of files. I've improved caching so it may help as well.

But I still do not know why with a single 1" you had so high power consumption Michael ...

Hello,
why I missed your previous post > do not know, sorry.

It is really weird because I'm aware of only two situations when track recording may be really paused "magically":

1) new, not yet perfectly working, mentioned "auto-pause" settings
2) app was killed by the system, and later started manually again (after more than 10 minutes after it was killed) and the app automatically pause the previous recording.


Otherwise, it may be paused over the widget, by intent (so over Tasker etc), in the UI (side panel or dashboard). Hmm and this is probably all ...

--

I've anyway just generated a new Beta version for tests so I've added some extra logs related to the start/stop of track recording. If you find a moment, you may try to install it, then long-click on the app main menu button and enable  Setup logging > Log to file.

Then try recording as usual and after the issue happens, so after you notice an accidentally paused track recording, just stop the app and send me a log file from the Locus/logs directory. Info, when (exact time) issue happened may be useful.

Zdravím,
může být. Bude přidáno v další verzi aplikace.