Author
Topic: Update of map core (2019) (Read 7887 times)

@menion. Understood now. However I think that means that the minimum zoom at which items appear in my themes will need changing for v4 maps. If you are looking at a remote area with few items to display it makes no difference. In a densely populated area it makes a lot of difference.

- shading is not working? Please, double check it's settings because I see no problem here.

@menion - double checked - see 2 maps - alpha & pro, both Hike & Bike theme, both same LoMap, both Hill Shading, scale as identical as I can make them. I note other subtle differences between the maps - is that to be expected? For example horizontal & vertical dashes green lines near "Wellington Park" only displayed with Pro.

Automatic Map switching works for v4-Maps now - nice! However, the map which was switched to is neither displayed in top bar maps display, nor in maps manager. There's always displayed the originally selected map.

Another thing: if I configure a vector map as an overly of another (or the same) vector map, the theme switcher shows a selection of which map's theme to change (nice!), but Locus crashes if I tap either of them.

Overall, great progress! I definitely think it's the right way to go, especially with the dpi-independend maps display!

@jonny.bluewhere I may download "Outdoor HD" theme to test the mentioned problem with LoMaps?

Problem with "staging server": login to normal geocaching server works correctly to you? What about at top of "Geocaching tools" screen, do you see there you avatar with a name and "right arrow" icon that allows to logout? Weird problem, indeed.

@john_percyright, 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.

Problem 43: will be solved in next version, thanks.

@Andrew Heardthank for "double check". I'll have to play with it little bit, because for me it works correctly. Anyway one more user confirmed same issue, so there have to be something ...

@zossebartright, 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.

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.

World map was limited to "zoom 8". I've moved this hardcoded limit up to "zoom 10" inclusive.

Zoom level indicator at top panel improved so in case, currently draw map will be this selected "world map" it will correctly reflect this.

Switching between LoMaps and OAM (or other V4 maps) was mentioned earlier in this topic and it's correct behavior.

Raster maps too big: all of them or just your world maps? Because here I agree, but it looks like you optimized your world maps to the good old Locus rendering system, right? As you may see on the screenshot from my Pixel2 device, online maps are quite useless on this device in Pro version and little blurred, but usable in alpha version. Same should happen with your world maps.

If you see them tooo big, maybe you have enabled rescale in settings > maps > Advanced features > Increase map resolution?

Hi Menion,I just compared same offline SQLITE map (which is a world map, but regardless ...) between Pro and alpha version: same map, world map and overlay disabled, the SQLITE map being the chosen one, no vector map in play..In Pro you need a 350% map resolution to show the same scope as the alpha version with 100% for same ZL.Any idea ?TXs and cheersMichael

@michaelbechtold350% is possible if you have some really XXXDPI device. Is this a problem? On devices I tested it, text sizes on vector maps and on raster maps are very similar now. This is thanks to the fact, that all raster maps now scale based on DPI, vector maps do this automatically since begin. And this is the point. Forget on a while on world maps you created and try some basic online maps and you should see the same picture as I posted before. The useless online map in the Pro version and correctly scaled map in this alpha version.

I got that, Menion (maybe a bit late :-) - see my 2nd post.Still, as a consequence there should be map scaling not from 100% up, but starting with 25% e.g. User have different tastes - and eyes ...The world maps I can adapt. I have to check other apps behaviour, too. Worst case make two versions.No big deal.

Oki fine.When I started work on this, I was at first thinking about an option, where you should set custom scale modifier for every single map separately. But in the end, it does not make to much sense. Ideal solution from my point of view is to unite scale of all! maps to the single same level ... so all maps should look same (we talk mainly about the width of lines and size of texts of course).

Then, everyone may use good old settings in app, to change the scale of all maps globally in case, he has worst eyes or any other reason.So I generally hope, this system will work, which should really simplify settings in app (no need to specify scale per map) and also highly improve usage of raster maps, that were quite useless these days on high DPI devices.Hope my explanation is clear .