Messages

3.38.3 first start with nullpointer exception and no map loading. Subsequent starts ok and look like v4 vector maps work again. Slower as v3 maps but acceptable. Edit: not even sure about this. I'd say GOOD JOB MENION. A big step forward. I am finally and exclusively using v4 maps and themes.
Expecting more bugs since this 3.38 is a big update.

Many thanks that we can turn off map smoothness. It's more transparent and direct this way.

And it runs great on my meanwhile very outdated Sony Z1.

No, same non-loading and white blocks with Elevate. As for VolUk, I am using Johns latest version he posted at the end of his thread here in this forum.

Crash gone. I switched from an sql vector map (topplusopen) to OAM v4 map/volUK - like 1 minute of white screen, I pressed zoom in/out numerous times... at some point map tiles appeared. Painfully slow.

I will not experiment. Want to avoid having to reconfig Locus if shit happens.

Yep, instant crash. Will downgrade.
https://drive.google.com/drive/u/0/mobile/folders/1U8U1D-NGQ9CAnqXAkleEXi46wH2T7tMR
Edit: don't know how. Will wait.

[@tapio]

@tapio
I've not implemented priorities with any consistency, certainly not different priorities for items according to the active style. I don't want to increase the size of the theme excessively and need to think about whether there are certain key items I should prioritise for different styles. I'm not sure if MF v5, which allows variables in themes, might help.

Oh sorry, I thought about if you could misunderstand my writing about the different sections. I didn't mean "priorities" in the technical xml sense, but in a general language sense. I meant that I was just wondering about general priorities in sections, i.e. the Hiking section shows hiking related POI sooner, Bicycle section shows no hiking route dots etc.

I think I like the brighter forest style, will see it "in the wilds" today

While map is painted, it is darker but then always is overlayed by brighter green. VolUk was darker before. Intended?

Ah, I was wondering if maybe there's some specific priorities in the different styles. I was using Allround, because I want to see biking/mountain biking routes. In order to avoid them, haha... 😂

Well, I had a look on the 2 raster maps I use. TopPlusOpen and Kompass. The size is pretty much perfect (a bit varying in different ZL). But I can see if Locus chose 2x instead 3x, it'll be too small again. I'd prefer to use it as it is now.

The custom algorithm is not possible. The whole logic is done in a lot lower in places, where I as app dev cannot touch ... somewhere deep in Android core.

But another idea, you could internally do a quality upscale when user downloads low resolution raster maps. You could do quality upscaling and offer such maps, if license allows, in your store and become wealthy.

Can you allow for a userdef rescale factor? I was thinking a long tap on bottom bar +/- could do changes to the map scaling. Could even be used for vector maps.
As for rescaling: Yes, before, raster maps had ant size, and now some raster maps cause eye cancer.
Maybe the used interpolation algo is crappy? For comic like imagery, I'd say raster maps would fit here, there is an awesome upscale algo called waifu2x which I used for upscaling Dwarf Fortress tilesets, with great results.
https://en.m.wikipedia.org/wiki/Waifu2x

Also, hqx. Probably it's all about performance.

That's great. Could you also please try the latest modded theme, in my previous post: https://forum.locusmap.eu/index.php?topic=2915.msg55516#msg55516

Yes, perfect now.

Since priorities seem to work, now I can create a fork again with some hiking related changes (benches, huts etc. at lower ZL, more prio to them)...

Finally I probably stop using v3 maps at all.

Again learned something new, long tap on themes...
Was my mistake, I put vol_res a level above the xml file, because it was like this before.
Thank you. Without your theme or Elevate, Locus makes no sense 😂

Thx you are really friendly ...

I do use voluntary mf v5 from last night and it has no trees.

Starting Locus and instantly sending Locus Actions makes it crash. In Tasker, I had to insert Wait.