Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Menion

#991
Guys, I'm glad you find new interface for BRouter useful. I was worried that this solution will be hardly to understand and also Petr with Michal was little "angry" for what I again did, anyway for now I've found it as best what I can do. So enjoy it, it won't be worst :)

@Bango903: hard to help, please read here, mainly part about creating logs. With such vauge description, there is nothing I may do.

@Joachim Buhl: we are talking here about manually clicked route where these via-points are on places where you clicked? This will be changed in next version next week.
The following users thanked this post: Andrew Heard
#992
Hi guys, version is out ...
this was looongest time between two major versions ever, I think. Hope list of news will have something interesting for everyone.
Thanks also for a valuable feedback, just please criticize (constructively), but don't take example from joeloc above and crtiticize at least few days before planned release. Better as soon as you discover any problem.
Thanks!

EDIT: ah! and thanks @gynta for neverending updates of first post with published versions. I almost always forget to update it :).
The following users thanked this post: Andrew Heard
#993
Troubles & Questions / Re: Locus Store
September 05, 2016, 18:44:54
Libor.. gynta has allowed almost everything :). Zuku it is usually almost impossible to help someone with quite old versions...

Sent from my SM-G930F using Tapatalk

The following users thanked this post: Jencek
#994
New Beta version 3.18.6.2
Many fixes already reported by users + first attempt to new version of "items" screen (available in menu > more) and first attempt to custom configuration for BRouter profiles directly over Locus.
Locus will now display also profiles stored in Locus/data/brouter (for those who wants to play with it). Such profiles also support "on the fly" definition of "avoid_motorways" and "avoid_toll" parameters. Check sample attached file if interested. Hope you find it useful.

@michaelbechtold: well, reason is currently quite simple ... because I have function "get me best vector map for this area", which is used in this case. Because all maps except LoMaps do not have precisely defined bounding area, it is little bit risky to use just a method "use current map". In such case, there is a chance, then map won't cover required area.

I'm sorry, for now I do not have a better solution. Because of this, it may end, that user itself will be able to manually choose a map, that he wants to use. Just an option ...

The following users thanked this post: lor74cas
#995
@lor74cas: I'll try to improve it little bit and allow to hide this button

@Bucky Kid: you see a raster map as background of this feature? Surprise, because only vector maps should be used here! And with chart > I'll try to do something with it, thanks.
The following users thanked this post: michaelbechtold
#996
27.06.2016 - Locus 3.18.0/3.18.1 - new version
- Blog post about major version: blog post
- Detailed list of news: list of news

30.06.2016 - Locus 3.18.2 - bug-fix version
- news after app start.

04.07.2016 - Locus 3.18.2.1 - beta version
- news after app start.

12.07.2016 - Locus 3.18.2.6 - beta version
- news after app start.

15.07.2016 - Locus 3.18.3 - more new version then bug-fix, but numbered as bug-fix
- news after app start.

16.07.2016 - Locus 3.18.4 - more new version then bug-fix, but numbered as bug-fix
- news after app start, as usually

22.07.2016 - Locus 3.18.4.1 - beta version
- news after app start.

28.07.2016 - Locus 3.18.5 - new version minor/bug-fix
- news after app start, as usually

03.08.2016 - Locus 3.18.6 - new version minor/bug-fix
- news after app start.

11.08.2016 - Locus 3.18.6.2 - beta version
- news after app start.

18.08.2016 - Locus 3.18.6.5 - beta version
- news after app start.

19.08.2016 - Locus 3.18.6.6 - beta version
- news after app start.

25.08.2016 - Locus 3.18.7 - new version minor/bug-fix
- news after app start.

26.08.2016 - Locus 3.18.7.1 - unofficially beta version
-

27.08.2016 - Locus 3.18.7.2 - unofficially beta version
-

29.08.2016 - Locus 3.18.9 - new version minor/bug-fix
- news after app start.

01.09.2016 - Locus 3.18.9.1 - beta version
- news after app start.

03.09.2016 - Locus 3.18.9.2 - beta version
- news after app start.

23.09.2016 - Locus 3.18.9.4 - beta version
- news after app start.

30.09.2016 - Locus 3.18.9.5 - beta version
- news after app start.

04.10.2016 - Locus 3.18.9.6 - beta version
- news after app start.

08.10.2016 - Locus 3.18.9.8 - beta version
- news after app start.
The following users thanked this post: Bucky Kid
#997
Good day Axles,
this feature was removed probably two years ago, because Google removed support for this feature for 3rd party developers. Thanks for understanding.
The following users thanked this post: Axles
#998
Pressing on map center can't be more accurate. All places except map center works as expected. But! Press on map center cursor always pick precisely map center coordinates even if you tap a few pixels next to exact center. You may try it on your own.
The following users thanked this post: wollewolle
#999
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:

    ....
    </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.
The following users thanked this post: michaelbechtold
#1000
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.
The following users thanked this post: wollewolle
#1001
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.
The following users thanked this post: wollewolle
#1002
Hello wollewolle,

feel free to vote for already existing idea: http://help.locusmap.eu/topic/filter-for-geocacheing-favorite-points
The following users thanked this post: wollewolle
#1003
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.
The following users thanked this post: sbouju
#1004
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.
The following users thanked this post: Andrew Heard
#1005
Quote from: gynta on May 19, 2016, 19:32:15
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
The following users thanked this post: Andrew Heard