New beta 7.0.3betaXXX

Started by orux, February 26, 2017, 09:15:17 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

eartrumpet

#15
Quote from: "orux"
Hello,



updated mapsforge libraries to 0.7.0 in last beta, may be you can test them,



orux

Same issues. With 320ppi device, all patterns work fine, with 440ppi only with OruxMaps 6.5.10 and earlier. Maybe it has something to do with fixed tile size? Maps with original mapsforge map viewer resize the tiles according to ppi, OruxMaps uses fixed 512px. But map elements like patterns, stroke sizes etc. are stilled scaled like they are supposed to (which is a good thing).

The scale factor for 440ppi would be 2.75 (440/160), so a tile size with 704px (256px*2.75) would be native (or when rounded to 480ppi -> 768px), which could break the pattern code. Maybe the scale factor works now (who knows why now and not before) only with smooth numbers like 3? Or at least 2.5?

orux

#16
Quote from: "eartrumpet"
Quote from: "orux"
Hello,



updated mapsforge libraries to 0.7.0 in last beta, may be you can test them,



orux

Same issues. With 320ppi device, all patterns work fine, with 440ppi only with OruxMaps 6.5.10 and earlier. Maybe it has something to do with fixed tile size? Maps with original mapsforge map viewer resize the tiles according to ppi, OruxMaps uses fixed 512px. But map elements like patterns, stroke sizes etc. are stilled scaled like they are supposed to (which is a good thing).

The scale factor for 440ppi would be 2.75 (440/160), so a tile size with 704px (256px*2.75) would be native (or when rounded to 480ppi -> 768px), which could break the pattern code. Maybe the scale factor works now (who knows why now and not before) only with smooth numbers like 3? Or at least 2.5?


I really don't know where is the problem;



In the next version I will adopt another strategy; Make the size of the tiles variable, multiple of 256 (256, 512, 768, 1024). Let's see if some problems are solved



orux

Joska

#17
Bug? Tried to change destination of maps. After doubleclick on ROOT in the destination-dialog, the line was empty and further no dest-path was available. Correction was possible, only by re-installing the beta-vers.



Joska

orux

#18
Quote from: "eartrumpet"
Quote from: "orux"
Hello,



updated mapsforge libraries to 0.7.0 in last beta, may be you can test them,



orux

Same issues. With 320ppi device, all patterns work fine, with 440ppi only with OruxMaps 6.5.10 and earlier. Maybe it has something to do with fixed tile size? Maps with original mapsforge map viewer resize the tiles according to ppi, OruxMaps uses fixed 512px. But map elements like patterns, stroke sizes etc. are stilled scaled like they are supposed to (which is a good thing).

The scale factor for 440ppi would be 2.75 (440/160), so a tile size with 704px (256px*2.75) would be native (or when rounded to 480ppi -> 768px), which could break the pattern code. Maybe the scale factor works now (who knows why now and not before) only with smooth numbers like 3? Or at least 2.5?


Hello,



Could you test this version-> http://oruxmaps.com/foro/viewtopic.php?f=4&t=4173&p=10922#p10922">//http://oruxmaps.com/foro/viewtopic.php?f=4&t=4173&p=10922#p10922



orux

6745th@web.de

#19
Looks good. I got 768px tiles on my Samsung S4 Active.https://uploads.tapatalk-cdn.com/20170307/a4ff0de339e78c294146c54d99d8b11e.jpg">

matt

#20
Good!

The issue with "pattern not fitting at some zoom levels of mapsforge maps", mentioned by eartrumpet, seem to be solved with OruxMaps7.0.6beta0.apk. At least on my phone (OnePlus One), where i was able to reproduce the "problem" in previous OM versions.



matt

6745th@web.de

#21
...and 9 times less files in the .cache folder  [emoji106]

Correct?