Messages

Thanks for an email Michale (btw, please change your support email to locus.map@asamm.com . Email you used is not longer used).

Seems you were a victim of one small issue on previous version. On the end of recorded track is one single invalid point. Exported file looks like:

Code Select Expand


    ....
    </trkpt>
    <trkpt lat="49.985613" lon="9.138136">
    </trkpt>
  </trkseg>
</trk>
</gpx>

Last point is without a time and other values. I'll try to fix it on Locus side, thank you.

Hmm probably caused by update of Android support library that has effect on stupid small blue down arrow in these selectors. It took now too much space. Anyway thanks guys, issue fixed.

[2.0]

Hmm oki ...

so in next version will be in config.cfg parameter map_items_gc_waypoints_lines_base_width

try to set values 2.0 or higher, this should help.

Hello wollewolle,

feel free to vote for already existing idea: http://help.locusmap.eu/topic/filter-for-geocacheing-favorite-points

Nono place is fine, it's not a problem. I just don't know what should I do here. Completely new version of Locus optimized on this tiny rounded screen? This is impossible task, sorry. Locus is too complex to be fully usable on such rounded screen and invested time simply doesn't worth it.

Hello Christian,

main key parameter for guidance that influence "when" Locus switch to next trackpoint is "Set next trackpoint" (in Guidance settings).

About rotation ... good observation. Locus filtered values from "before" screen turned off. I've fixed it now. Result is quite visible jump in rotation right after you turn screen on, but positive is, that you see it almost immediately. So "fixed", thanks.

Hello Petr
We talk about "house number sorting" in march 2016. do you remember?
I think alphabetical sorting arrays will be work. Let's try
Currently we have a wild mixed list.

done

@Andrew: hmm I'm almost sure that my small change should have no influence on this. I may disable it, as it's just one line of code, but it really should work without a problem.

Do you have exact steps I may follow to get exactly same problem?

I'm trying to play with it little bit, but GPS is always turned of correctly in Locus, hmm :/.

EDIT: maybe I've found some weird combination, so next version probably during weekend, thanks

[16.05.2016 - Locus 3.17.0]

16.05.2016 - Locus 3.17.0 - new version
- Blog post about major version: blog post
- Detailed list of news: list of news

17.05.2016 - Locus 3.17.0.1 - unofficial beta version
- ...

20.05.2016 - Locus 3.17.0.2 - beta version
- Changes: read news after app starts...

22.05.2016 - Locus 3.17.1 - new version
- Changes: read news after app starts...

22.05.2016 - Locus 3.17.2 - new version
- ...

01.06.2016 - Locus 3.17.2.1 - beta version
- Changes: read news after app starts...

10.06.2016 - Locus 3.17.2.3 - beta version
- Changes: read news after app starts...

18.06.2016 - Locus 3.17.2.4 - beta version
- Changes: read news after app starts...

24.06.2016 - Locus 3.17.2.8 - beta version
- Changes: read news after app starts...

Hehe, oki guys, you are welcome. To make it more "fast", after save of changes, screen will be closed back to map. Hope it will be ok. And btw. do not forget to enable this button in settings, because I left it disabled by default.

Hmm, this isn't what I wanted to hear . Implemented.

[previously]

yep. It really just preselect tha ONE item you long clicked. Nothing more and it won't have effect on visibility/selection of other items. So in case, you have visible a lot of points/tracks on a map, but wants just select two of them, you had:

previously: tap on bottom button, in top toolbar tap "selection button" > deselect all and then tap on wanted two items
now: long click on first item, then select also second item

Hmm sounds good. Thanks for help.

Hmm good point. So to make it "different then bottom button" and more useful ... just long-tapped item will be pre-selected. Not all currently visible + long-tapped. Agree, done, thanks.

Hmm interesting. Truth is, that I woke up by accident after midnight and noticed this message Andrew & Micheal, thanks for it, so I've published it correctly a lot later (forget to press "publish" before. Did some test and then leave on a cup of tea ), but now it should be there!

[EDIT]

Quite a mystery for me. I spend on it two hours and I'm still unable to find out, why this happen. It should be ellipse, but not so big. Interesting ... so next try again after few months probably .

EDIT: damn, I don't like such mysteries ... solved another two hours later. Thanks