@
jusc: I don't know where is feedback from testers. I have one major benefits from testing - if Locus seriously crash - "Force close", I receive report with this crash log. So I can try to find where is a problem. If users do not comment or react on this new version, only what I may think is that everything is OK or they don't care. So because except few posts from you, I had no negative reactions on new track record panel, I believe, people don't care or like it.
Other use cases as you wrote - I belive we may togetger find 100 possible activities, where you may use track record in different way. I always try to find optimal solution which will be somewhere between all possibilities.
My first idea was to create completely separate screen just for track record, but it was even slower during field testing because there were no ability to show/hide with slide. So this was something between.
I don't know who except you still have problems with side panel. I personally found it very useful during ride on bike. Bottom panel on map with it's tiny buttons is very hard to touch during ride, almost impossible. So you still always have to stop to tap on any buttons. With this side panel it is not a problem. Hmm anyway, may you describe me what you do with "track record" feature during one day bike ride? Because maybe this may help me understand why you need to have this panel still visible.
@
balloni: 2. hmm I wrote it somewhere ... mnt. Ah just partially here
http://forum.locusmap.eu/index.php?topic=3796.msg29355#msg29355 , sorry. So on chart, you see only last 100 points, no more. This limit is there to prevent bigger CPU usage due to some computations needed on bigger charts. Anyway I was thinking about it, and in worst case I may create this parameter configurable by config.cfg
3. sorry, not possible now. Track record is created with exactly same method as a dashboard you create. So what isn't possible in dashboard, isn't possible here.
And offlinizer - I wrote it incorrectly. Better description:
Current Locus version (official):
1. you import any cache, display it on map. Till now, nothing happen.
2. You tap on cache, now you see new screen with point details (geocache details).
3. Locus display listing and Android WebView component starts download images to it's own cache.
4. .. then you check few more geocaches and every cache download it's images to WebView cache. This cache is limited to 10 MB, so when it's fill, new images overwrite olders.
5. You display again first cache and Locus needs to download these images again!!
New Locus Test version:
same steps, except
3. Locus display listing and Android WebView component starts loading images - here anyway comes my code which firstly download all images on card (same directory as GC Offlinizer). And then add these images to WebView.
5. Same point, but images are still cached on card.
This feature is anyway in "DEV" part, because I saw some small problem with reloading of webView page after images are downloaded, so I have to be firstly 100% sure, it work as expected.
Better?