Messages

Hello Bernhard,

the sensor I use most probably does not support dual-mode (only a single sensor on the bike), so I can't test it directly. Also, I'm not sure, what to do with the "balance" value.

Anyway first test: in the next app (also in the next Beta version), the value should be visible in the "Sensors manager screen" when the sensor is connected.

So if you find a moment, give it a try and let me know, thanks.

Thanks for the link. 141MB of GPX files ... quite a lot. I expected that the app could handle it, but it ended with an out-of-memory error. Something, that should be solved on the app side, but it requires quite a lot of debugging.
So problem is registered to the "Problem to solve later" category. Thanks for understanding.

---

Extra DB, please no. You can't convince me because this should be solved by the already planned feature I've mentioned above.

[@Andrew Heard]

@Andrew Heard
"Error when nav points are close" > better error is of course better , but I need to simulate it to set up and verify the correct error message.

"Font size" > I hoped it would be possible to temporarily reduce the size of the font for the whole tablet. This is the default size? We talk about your Tab A7??

@Tapio
Import of 850 files > heh, I do not have so huge amount of files to test  . May you share with me this problematic pack?

---

Database size
A secondary database (archive) is not planned, sorry.

Anyway, what we discussed is improving sync logic.
Currently, all data needs to be on the device and if "sync" is enabled, all are synced to the web. What we plan (it may change because we mostly discuss it for now), is to offer options like:

- keep folder local, sync (currently all folders)
- keep folder local, does not sync
- local folder data on demand, all on the cloud

I'm checking your steps and see a few problems there:
- The "Search button" missing on the keyboard when searching for points
- The last selected folder in the search is not preserved
- The "Navigate to" screen is deprecated and will be removed soon (I hoped for this month, but it looks more on February next year)

Anyway, when I choose for example "Touring" bike, the next time this "Navigate to" screen is visible, the correct profile is preselected. Interesting.

None of the problems is easily solvable. The search screen waits for deeper integration to the new search system and "Navigate to" will be replaced by improvements in the Route planner. A little patience and I'm sure, your workflow will be improved .

Uff
Díky též za test a trpělivost!

Old topic, sorry ...

Analyzing and .. interesting problem.

The last point of the "Startteil..." route has an almost identical location as the first point of the original recorded route. This is probably what you wanted. Because of this, the app refused to insert a space (break point) between them and the result was, that time was from "0" (1. 1. 1970) till the day of the second route. This was not the case of the second manual route, where the last point was not identical.

I've improved this behavior, so it should be better in the next app version.

[@Tapio]

Ah, damn, it's enabled. I forgot on it (had it enabled during development). Sorry sorry, the fix is on its way ...

@Tapio
it already may be available for hiding! (ah you already found it)

@Andrew Heard
Android 11+ maybe? Not sure now, but yes, some requirement is there

[Locus Map Beta 4.20.1.1]

Locus Map Beta 4.20.1.1 (test version on Google Drive)

with surprise for @balloni55 and probably also others

Have a nice weekend!

And I've again merged posts into this one topic, sorry

This is not so easy task to do. As you may see, even online maps in the Android app do not have this feature. Because online maps are currently based on the raster (so simply JPG/PNG pictures), it is not possible to modify it's content. So maps without hiking/cycling trails means second web server that will supply "duplicate" map. Very expensive solution!

Because of iOS version we are working on (not just), we are discussing the option to use vector data also for the online maps! Well better > we will have to use vector data for online maps soon or later. This will allow us to also quite easily implement this feature.

It will take some time, hopefully not much. Locus Map for iOS is already prepared for online vector maps. Web planner will be for sure during next year and Android ... hmm, it will be harder, but in the worst case, Android may still use raster data ..

Hope my explanation is clear. Feel free to ask if something is not clear ...

[@slarti76]

@slarti76
ah!! Thanks for the video. I was talking and checking the behavior of the "Stop" button in the panel (as visible on the screenshot). You were talking about a small button directly on the main map screen.

As I see, the current behavior was implemented at 06/2022! and no complaints since then. Long-press simply calls "Stop" and the recording service takes care. In your case, seems you use auto-save, so the result is quick and correct from my point of view. Do you have some accidental clicks on this button?

[@slarti76]

@slarti76
This simply isn't possible  .

Are we talking about the long press on this "Stop" button? There is a simple method that have to display "Discard" question dialog.



@Andrew Heard

issue with "Save & display" settings > can't do more now. Will have to test it and simulate it.

issue with layout > ah thanks, got it.

new settings in Preset > there are a lot of such ideas that make sense for a few users on the help desk. So maybe later when I'll be working on presets.

Thanks @ta-ka , you are correct. I've tried to re-use existing text.
For now, I've removed this header from the dialog at all.

[@jonny.blue]

Thanks Michael,
unfortunately, the version with a fix (problem with choosing a routing profile), that came an hour later, was not refused by Google, again because of some insufficient informing of users about subscription, omg. So, most probably one more version will have to be published next hours/days, who knows? But nothing serious. The version on the Drive is perfectly fine to use. Sorry for this mess. 

@jonny.blue & @AgusOrux
hmm, perfect, at least something positive!

---

Uff, hopefully with 4.20.1 (1121) version, all major problems are solved. Thanks and have a nice weekend!

Sorry Michael, I discovered one minor issue right after release, so I've immediately republished the new version 1120. Uff ... 

[Locus Map 4.20.1 published]

Locus Map 4.20.1 published.

Available over Google Play or the Drive directory. I've made a bunch of various fixes, so hope it helps.

@jonny.blue & @AgusOrux
Unfortunately, I'm unable to simulate your issues. If the new version does not help, I'll need a full bug report right after the crash happens by this method. Thanks.