Started by argus, November 27, 2011, 19:12:59
0 Members and 1 Guest are viewing this topic.
Quote from: "menion"Hi mdmystko, I just few hours ago discovered also that Locus do not remember items. It's issue caused by merging points/tracks/items into one screen. This is already fixed and will be working again in next version
Quote from: "menion"anyway about usability. You see some changes in last version when loading images from KMZ files? It's correct that Locus is trying to load all visible! images from KMZ files at once, but all are reduced to only required size and also all are throw away immediately when not needed.
Quote from: "menion"...I really suggest to set as a background "Online > Blank" map, which take almost zero memory so quite useful in your case. Also handy should be "reduce visibility of recorded points" (in settings >track record) to some lower (100 - 1000) number. It will also save some power and memory
Quote from: "menion"solution on this is simple - just rename little bit your KMZ file ...
Quote from: "menion"anyway this is quite weird. I added into Locus small protection mechanism against huge KMZ tiles. What KMZ map are you using? Is publicly available, so I can test it?
Quote from: "menion"please check this test version https://dl.dropbox.com/u/8015949/Locus% ... .6.1.1.apk. I found small bug in resampling, so maybe this will help on crashes.
Quote from: "menion"But about quality it's interesting. Only thing I changes is that now images should be little bit blurred (anti-aliasing enabled)