Messages

Are you sure? Just check the content of the generated zip backup. Presets should be there (directory data/presets).

Yes, I'm sure, I checked the backups of several devices, all only included data/config (plus config*.cfg and _various). Mind you, talking about the "settings only" backup, the full backups contain the presets alright.

One thing about the backups I just stumbled over:
When I do the "Settings only" backup, it diesn't include the "presets" folder. That kinda seems wrong to me - presets are a very important part of settings system, I'd say.

With the new UI design, the "Nearest Points" sidebar looks a little odd and wastes space: There's a lot of white around the rather small icon, thus cutting off the text more than needed. Also, when a point is selected, you can see that the text cuts off without any pixel margin to the blue background of the "selection eye". Doesn't look nice.

I'd also like to take the opportunity to repeat that selecting/deselecting points from the sidebar is still far too cumbersome. There should at least be a Select All/Deselect All, even better would be "Select within x km radius". I find myself clicking on dozens of points all the time to see what's of interest in the currently centered area.

And tasker task ... if you have any task hardcoded on certain activity within Locus then yes, this is broken with current version.

Did the intents also change (like com.asamm.locus.ACTION_TASK)?

Free & Pro simultaneously ... problem is in detection that something like this is happening. Generally in Android is nothing like "app is running" and "app is not running". Well, Locus Map tries to simulate this behavior, but it is more a hack then suggested method. So one app cannot simply say if any other application is running. And in case of track recording: current recorded track is save directly into internal memory to cache directory to prevent some possible loss because of unexpected situations. And this cache directory is shared between both versions. For most of other features, there should be no problem.

I experiences this too on the weekend: Had to change phone battery, after restart Beta & Pro were both showing notification about unfinished track recording. Now that was rather aestethic, but tbh I was afraid to stop the recording in one app for fear it might also affect the (already unpaused) recording in the other. Is there a danger?
And couldn't you just write a tag in the file to say who started it? At least in the above situation you don't need to find out if the other one is running or merely installed - just make sure that Pro continues a recording started by Pro and the same for Beta/Normal.

[@tapio]

@tapio
interesting issue with the long click on track preview. This issue has to be there since the beginning. If you put finger away in the moment, the overview is generated, it works correctly. If you hold it longer, it causes this problem. I know why this happens, but with this old system, I currently do not know how to solve it, sorry.

I know I've also always been bothered by this: If you don't press long enough: Details - if you press too long: Regeneration plus Details. You have to time it just right. I think there was a time when the too-long-press didn't go into details, but I'm not 100% sure.
Anyway, there's more important things

[@slarti76]

@slarti76
yes, it is what you see. Among that, I've united background system so add-ons and internal location sources are in one big grid. It is also possible to enable/disable all available sources under same place. Sorting is possible with drag&drop.

Well, I tried to D&D in the Edit-List, which doesn't work - have to do it on the screen itself. There are other lists in Locus where you can D&D directly, that's what got me confused.

The release notes for new beta said something about "improved system for pick of location". I only see a few more options and possibility to remove custom points - is that what is meant or is there more I'm not seeing?
Anyway, could you make that list sortable? That would be a nice improvement...

I know this is not a usable bug report, because I don't have a recipe to reproduce. It's more I'd like to ask the community if they are experiencing something similar:
They more I play with changing maps, zooming in/out, turning map shading on/off, adding/removing overlays, the more often it happens that Locus displays tiles from other maps. As I said, not reproducible with easy steps, but I think it happens more often in recent releases (perhaps related to the big speed-up, but might have been before).
Of course I cleared map cache, but it still happens.
Anyone else?

One thing that has been bothering me for a while:
In the "Points of Interest (BETA)", why do I still have to select the region myself? You can determine which maps are fitting for the currently dsplayed area, but not which set of points?
I do get that putting all points together inone big database (internally) is perhaps a little slower, especially on older devices. But it should be possible to select the Points DB "Honshu" when I'm just displaying the Locus Map "Honshu"...

EDIT: Looks like tapio is complaining about the same thing and I didn't see that. Anyway, I'm not the only one

[Beta 3.38.5.1]

*** Beta 3.38.5.1 with a bunch of updates & fixes *** (not just problematic navigation).

Magnify now works flawlessly and as expected, didn't have any hiccups in (admittedly short) test. Thanx, great!

But I have one complaint:
Hiding the "world maps" from the Quick Map Switch is a NO-GO like this: I have a downloaded Google map with a wide zoom level range (7-21 or something) that is now hidden. It's my main offline map! Please don't hide maps that also contain high zoom levels.
Good opportunity to point to this again: https://help.locusmap.eu/topic/flag-to-hide-maps-from-quick-map-switch - definitely the more flexible solution...

[@tapio]

@tapio
correct, I still believe current behavior works correctly. As I wrote, there is a need for one tiny change that causes a little trouble for me. If you set 150% to magnify, the app just needs to do zoom by this 50 % (like by fingers) and then all will work as expected. Anyway, let it be for now, I'll invest more time to it and in next Beta ...

It's slarti76 Nevermind...
Tried out 3.38.4. First tried with 200% and 300%: Absolutely identical maps displayed. Then tried out 150%: No change between 100% and 150%. Then, as you hinted at, zoomed out and in again: Now it looks like it may be 150%. Tried out 200 and 300 again: Now there was a difference.
At last, tried 400%: Different to 300%, but muuuuch bigger.
Now I noticed the percentages shown in the top bar. At base resolution (no magnify), it showed "200%". Ok, probably a result of the DPI calculation, whatever. With magnify to 300%, it showed "500%" (which is 2.5x=250% magnification). At 400%, it showed "1000%" (which is 5x=500%).
No it struck me: The problem here is, I think, that my map doesn't have linear zoom levels, the highest levels are "1:50000", "1:25000", and "1:10000". I assume that when I'm in the "1:10000" level, that messes with your calculation, as you expect the lower level to have half the resolution (1:20000) and calculate the level to be used for magnification and the enlargement of tiles based on that - which has to fail.
With a Google map download done by Locus, I don't have those severe discrepancies, but there's also no difference between 250% and 300%, for example.
Also, when I zoom in more than the highest zoom level (one or two additional taps on "(+)"), I'll still get to a point where Magnify has no effect.

So in summary:

• The algorithm seems to break down when the map's zoom levels are not 1:2
• Magnifications between full 100% steps are sometimes a problem*
• Magnifying when already magnified in highest zoom level doesn't work
• Sometimes magnification is not applied directly, only after another zoom in/out

* I think it would be no loss to get rid of the 25% steps, and also all 50% steps after 200%, but at least 150% should work.

Hope this helps.

PS: Good news: Didn't have any blank screens anymore

[@slarti76]

@slarti76
I'm still quite sure it works, it only does not immediately change what you expected (visible camera scale). Try to use hardware zoom in/out after you change magnify and you will for sure see difference.
Anyway blank screen with combination with zoom lock is weird. Can't simulate, but will be watching it.

Ok, I recorded a screen video, showing how it sometimes works, sometimes doesn't; plus an instance of blank screen when magnified. "Unfortunately", the factor worked in this case, but I did try it before with screenshots where the result was always the same no matter what factor I used. Can't figure out what was different.
Download: https://web.tresorit.com/l#CfD2qKZB6nRcAjJFGdbFCg
Corrected: https://web.tresorit.com/l#PVxxuyumpUpuQjSiiSCFmA

Beta 3.2, "Magnify all maps"
The severe bugs from 3.1 are gone (no blank tiles/screen), but apart from that it's still not working as advertised. I'll summarize:

• Factor has no effect, always seems to be x2 (vector and raster maps)
• Raster maps: When in highest available zoom level at 100%, and I zoom in once, it enlarges to 200%. When I now switch on "Magnify", nothing happens. Things get even weirder when I use "Lock the zoom" - then I even get blank screens again. The current algorithm clearly doesn't work when in highest zoom. Probably also the case for vector maps, but there the highest possible zoom is so large that it probably doesn't matter that much. But with a raster map with max ZL17, it is!

New Beta 3.1:
"Magnify all maps" totally broken for raster maps: sometimes screen is just white (downloaded Google Maps), sometimes it works, sometimes no change at all (still in highest available zoom level). Magnification level still makes no difference. For vector maps, it basically works, but also with always the same magnification.
Sorry, unusable. Restarted several times, cleared cache, just to be sure, but that's not it