Update of map core (2019)

michaelbechtold · April 10, 2019, 11:16:05

I was also assuming a single scale setting (like today); my only point was to not start with 100% (as today), but with 25%.

zossebart · April 10, 2019, 15:24:10

Quote from: menion on April 09, 2019, 13:28:14
right, autoloading works this way. First selected map is something like "base map" and all other "autoloaded maps" are just added into some kind of inner container. So you will still see first selected map. Which, as I though about it, is correct ... highlighted and also restored after restart, is still the map you selected.

Ok, understand. I just recognized that the behavier is different to the current version.

Quote
Two vector maps at once as overlay: do not expect too much from it. If both maps will be V3 or V4, they use same single instance of map theme so cannot choose different themes for them. Anyway I do not get any crash so I'll need a log here, thanks.

I don't know if this is useful, either...just played around a bit because you wrote nearly all combinations are possible now.
When I did this and wanted to change theme, I got a selection what theme to change (see screenshot). However, in both cases, Locus crashes. Is it intended to have this selection or should it be removed and only offer theme change of base map (as it is in current version)?

I now also tested online raster maps with alpha and it is a huge improvement! Nicely readable now!

Gesendet von meinem D5503 mit Tapatalk

Martin_ · April 10, 2019, 20:52:02

I noticed that switching the map language on a V4 map requires a restart of locus to apply the new language. The second time I changed the language, a restart was not enough and I had to clear the cache/perform a second restart.

john_percy · April 10, 2019, 22:21:55

Quote from: menion on April 09, 2019, 13:28:14
@john_percy
right, in case you will want to use your theme optimized for V3 maps, in new V4 maps system, then you may see a difference in how soon certain items appear. To be true, I'm not 100% sure how this affect real usage so best to give it a try and you will see yourself.

Here is an add-on alpha version of my "Mapsforge Voluntary" theme. Download, extract, and add to an existing Voluntary theme installation to get a "Mapsforge Voluntary alpha" theme for MFv4 maps in Locus Alpha. Zoom-mins and scaling have been tweaked to make its appearance closer to the theme on LoMaps/MFv3 but how well it does this depends on the resolution of your device.
Please let me know if I am on the right lines with this.

john_percy · April 12, 2019, 11:41:16

Also, Quick Map Switch "Last Used" online map and Map Manager "Last Map" don't update last used maps now. Possibly connected with maps in custom providers file?

Sent from my moto g(6) plus using Tapatalk

Menion · April 12, 2019, 14:30:39

Hi,

New ALPHA version

uff, a long week filled with work on this map system. I believe that all reported problems here should be solved, so give a try to new version (link in the second post). Thanks all!

john_percy · April 12, 2019, 14:56:51

My issues so far are resolved.
Maps Manager / Smart Choice / Online / Most Used seems stuck and gives the wrong maps.

Sent from my moto g(6) plus using Tapatalk

Menion · April 12, 2019, 15:09:36

Here may be a small issue in fact, that Locus counts usage of all maps since begin. So some maps were maybe used so frequently, then now that are always first in the list. You may try with clear list if you manually delete Locus/data/config/map_usage_counter.lb file.

john_percy · April 12, 2019, 15:25:24

Hmm. Deleted that file, restarted phone. Same results, which do not reflect my usage recently or from the start of using Locus. File reappears as 915 bytes with today's date.

Edit: the same file is also shared by Locus Pro, which reads it correctly.

Menion · April 12, 2019, 17:28:27

Ah ok, thanks, I'll check it.

jonny.blue · April 12, 2019, 18:57:16

Quote
New ALPHA version

Geocaching problems are solved ... 😎

john_percy · April 12, 2019, 19:40:37

1. Why are there ghosted themes (originally for MF v4 maps, now for MF v3 as well)?
2. MF v4 themes are not optimised for MF v3 maps not do they look the same as on V4 maps - is this to be improved?

Sent from my moto g(6) plus using Tapatalk

Menion · April 12, 2019, 20:25:21

Hmm this better discuss with @SwissPopo and mainly @Tobias

It started here: https://forum.locusmap.eu/index.php?topic=6471.msg54754#msg54754

I'm not an expert in this area. V3 themes should work correctly on V4 maps and also opposite. On the second side, agree that there may be some "optimization" and same themes may look different in V3 and V4 renderers (and this I can't simply change).

When we speak here, I would also vote for not offering V4 themes for V3 maps.
And because V4 maps are now scaling based on device DPI, I would also vote for the old system, so not to offer V3 themes (and older) for V4 (and newer) maps.

If someone will want to offer his theme for V4+ maps without any extra work, he may just update the version in theme definition on own risk. Feedback?

john_percy · April 12, 2019, 20:33:10

I would agree about not offering V4 themes for V3 maps. The scaling doesn't work. Caption position appears not to be supported, though that could be sorted, I guess. There may be other points but I've not looked closely.
That deals with my point 2. As far as my point 1 is concerned, I don't know what the ghosted themes represent. Are they folder names?

Sent from my moto g(6) plus using Tapatalk

Tobias · April 12, 2019, 20:36:41

I also just checked the new version, the rendering of V3 maps with V4 themes is wrong.
What renderer is used for V3 maps with V4+ themes? If it's the forked 0.3 version (locus-extended) it makes not a lot of sense, as at least mapsforge 0.5+ is needed.
I would propose checking the theme version in the xml-file, if it's version="1" and/or locus-extended="1", use the Locus-Fork, if it's version="4" or higher, use the standard engine.