This object is in archive!
Track previews not correct when map zoomed
Solved
Sounds complicated, but pretty simple bug:
- Lock the map zoom
- Zoom out such that normally, a lower zoom would be used
- Force redo of a map preview (e.g. by editing a point and then viewing the track data)
Now, instead of a preview of the whole track, only a part is seen (if at all).
Bonus question:
Is there a way to determine which map will be used for the preview? It doesn't always seem to be the one currently displayed, at least not if it's a downloaded map. Instead, it must be some other, probably vector map. My tracks are often in the mountains, where the OSM maps show not much, it would like to have the previews use my SwissTopo map. But I don't get it done...
The same problem 
Hi Ingo,
uff, this one was quite complicated. Anyway issue fixed, thanks. So in next version, preview won't be affected by scale value from main map anymore.
And bonus question - right, all previews are generated from vector map available for certain are. No other options are possible and even planned for now, sorry.
Hi Ingo,
uff, this one was quite complicated. Anyway issue fixed, thanks. So in next version, preview won't be affected by scale value from main map anymore.
And bonus question - right, all previews are generated from vector map available for certain are. No other options are possible and even planned for now, sorry.
Thx, quick as usual :)
The thing with the used map is also fine with me, I just wondered if there was a way to force Locus to use another one. But in the end the shape of the track is the most important thing anyway about these previews.
Thx, quick as usual :)
The thing with the used map is also fine with me, I just wondered if there was a way to force Locus to use another one. But in the end the shape of the track is the most important thing anyway about these previews.
Yes I also think that shape is what is needed here. Anyway I've at least added double resolution to these previews to next version so they will looks little better (track and map will be smaller/thinner).
Problem with custom map is in inaccurate detection of borders. Also it will require some extra settings etc etc. Many things around. Using vector map is most simple solution.
Yes I also think that shape is what is needed here. Anyway I've at least added double resolution to these previews to next version so they will looks little better (track and map will be smaller/thinner).
Problem with custom map is in inaccurate detection of borders. Also it will require some extra settings etc etc. Many things around. Using vector map is most simple solution.
All fine in 3.12.1 - thx!
All fine in 3.12.1 - thx!
Perfect, glad to hear it.
Perfect, glad to hear it.
Replies have been locked on this page!