@pmoravec: updating and whole handling of locus data over Locus API is based on points IDs and when arcao in G4L update cache, I think he update it thanks to GC Code of every cache. So there should not be a place for such huge issue. Anyway are you able to reproduce it? Even better - are you able to give me step by step instructions, so I can reproduce this?
@jusc: thanks, picking a maps fixed
@druki: yes, lines are drawn just from first point to intersection. Anyway I warn you, this computation isn't much precise. I'm still searching for more precise way to compute it (currently I approximate compute on sphere and not on ellipsoid). About additional information - all these line/circle draw functions has big disadvantage. After you draw something, this item cannot be selected and used. Locus also do not compute some intersection between circles automatically etc etc ... so there is big place for improvements. On second side, I think these functions are really rarely used, so I still have no reason to invest too much time into this ... and it's same with your request on display an azimuth and bearing.
@henk: I think it's just ... "luck"
@druki, tramp: I also had one crash when I wanted to stop navigation, but I'm unable to repeat it now, damn. And tramp, your problem with battery consumption is really very weird. Mainly because it's almost impossible to consume battery when Locus is not in list of apps. I would like to publish final version before release for some testing. I'll then need some time, so priority is to release version without problems. So please check it and create for me a logcat if some problem happen, thanks
@druki, gynta: hillshading ... if this will work, it will be amazing
. Anyway same as on some other places ... I still wasn't able to create fast method for this hillshading, mainly on lower zoom levels. It's of course possible to change sun angle (I'll do it, thanks), but this will still not be enough to make hillshading nice looking ...
