[APP] - version 4.29.+ ( 4/2025 )

[Menion]

@Andrew Heard
overview for copy > should be fixed now, thanks

@Graf Geo
track preview > hmm, please check the style settings of your line. What width value is defined there?

10100 error during search > when this happens? In normal search? Give me a text you enter to simulate this problem, thanks.

@Tapio
more complex work with "highlighted LoPoints" > I'm still not sure to be true. Maybe I'll keep it as simple as possible for now. We will see 

@balloni55
blue bar > app loads full point detail. But you've found the issue for points with a defined area, I'll fix it, thanks! It is the same issue reported by @Graf Geo here. Btw. probably best to keep issues in Beta on the forum. On the help desk, it is created as task for Michal who in the end, returns the issue to me 

@Agus
HR monitor > and this worked before? If you see the item disable in the list, it means that the is item cannot be connected to. Maybe disable/enable the sensor and try it again?

@freischneider
suggestion of categories > agree. We need to implement some kind of history for the offline world as well.

@40°
a little harder for me to simulate, but probably an identical problem to what @Graf Geo wrote. Does it happen always for the same inserted texts?

[Agus]

@Menion I had the same problem a few months ago.
https://help.locusmap.eu/topic/34184-i-cannot-select-heart-rate-monitor

[Graf Geo]

@Menion:

@Graf Geo
track preview > hmm, please check the style settings of your line. What width value is defined there?

10100 error during search > when this happens? In normal search? Give me a text you enter to simulate this problem, thanks.

Track preview: At 3 px (I use this for most tracks) the line in the track preview is a bit thin. But I checked it again and the thickness is taken over. So ok. Even if it looks very different in proportion. See screenshots. Setting for testing: line thickness 50 px.

10100 error: As I wrote, it happens very often when searching for categories:
Search -> Source category -> Whoops!

Ah - I think I know now when it happens: If no corresponding object of the searched category exists in the current map section, the 10100 error comes up!
Easy to reproduce: Zoom strongly into a body of water or a Forest and search for a category that certainly does not exist there, e.g. food & drink or restaurant. If you zoom extremely into a lake so that the screen only shows a light blue area, the error message will of course appear for every category.

So the error message is nonsense, it should read: There is no element of this category in the current map section.

[Menion]

@Agus
very interesting, thanks. You wrote that the issue disappeared in a certain version of Locus Map. I've made no changes in the Bluetooth implementation on the Locus Map side, so it is weird that something changed. It anyway should not be caused by the app, sorry.

@Graf Geo
the difference in width is correct. App try to generate a preview independent on the device resolution.

Simulation of the search: ahhh, nice, thanks!!

[40°]

a little harder for me to simulate, but probably an identical problem to what @Graf Geo wrote. Does it happen always for the same inserted texts?

Error 10100 occurs if you select "Online addresses and locations". Any text.