Hi to all at the start of the new year 2019,
more and more (advanced) users complain about little weird support of the latest version of MapsForge maps (V4+) in Locus Map app. So let's move with it?
I would like to ask for help here. First I need to better understand current problems with the support of latest MapsForge lib in Locus Map. From this, I would like to create a list of tasks that need to be done and set priorities. Please be short, be clear (or point me to already existing clear and short post).
I'm sure, that most of info was already wrote somewhere here, but to be true, I'm still confused about this topic. Thanks for understanding and help.
List of current known problems
more and more (advanced) users complain about little weird support of the latest version of MapsForge maps (V4+) in Locus Map app. So let's move with it?
I would like to ask for help here. First I need to better understand current problems with the support of latest MapsForge lib in Locus Map. From this, I would like to create a list of tasks that need to be done and set priorities. Please be short, be clear (or point me to already existing clear and short post).
I'm sure, that most of info was already wrote somewhere here, but to be true, I'm still confused about this topic. Thanks for understanding and help.
List of current known problems
fixed 256x256 tilesize, should scale based on DPI, more info- solvedhardcoded usage of themes V3 maps = V3 themes, V4+ maps = V4 themes- solvedmultiple themes per directory- solvedmissing auto-loading- solved, seems to be little slow when more maps is loaded, but works- problem with hillshading system, more info
- incorrect redraw of text labels after zoom, more info
- support for MapsForge POI