Messages

There are dozens of usefule gps trip & tour portals (gpsies, wikiloc, and plenty more). Some "work best" in one country while others are used in other countries. It would be great if Locus could "interface" their web sites by offering them in the sharing menu via customzied URLs:

I would configure something like
name: wikiloc
url: es.wikiloc.com/wikiloc/map.do#lt=%LAT%&ln=%LON%&z=%ZOOM%&k=2&tab=0&a=2

Locus could then offer "wikiloc" as sharing option for the current screen position and I could with a single finger tap find out what routes are available.

Of course Locus needs to offer multiple options here.

For a start, how about config file entries instead of a complexish settings GUI, at least until we figured out what makes sense and if this feature is actually usable:
urlshare1-name, urlshare1-url,
urlshare2-name, urlshare2-url,
urlshare3-name, urlshare3-url,
...
Obviously, Locus must ship with reasonable defaults for the most well known trip portals. I am sure, people will find other uses for other websites as well. DOesnt necessarily have to be trip portals. Only important thing is that the URL is completely customizable.

Ok.... that makes sense. Unfortunately it doesnt help in finding my buddy. Maybe simple locus-internal buddy tracking will come even before kml panel. Or an implementation of googles latitude layer :-).

I quite like the builtin hillshading from hgt... good job!

Is it possible that "Center Item" in Locus map elements context menu does not work on network links like the kml created from gyntas test service? How can I find my buddy then?

Ok... understood. So all will be fine if I delete those three offending files? You probably wouldnt have to rescan 20 good maps if 3 bad maps are discovered, but hey... thats nitpicking :-).

Anyway... about the xml files: they come from http://www.openandromaps.org , the best and most complete and prettiest source of mapsforge vector maps for hiking and biking. Every downloaded map is accompanied by exactly one xml file, which I guess contains rendering information for Oruxmaps. The file is not needed for Locus obviously because you have the styles done differently.

However, some people (including me) have a dual installation with Oruxmaps and Locus... you know why :-). It would be nice if you could simply ignore those xml thingies in the maps folder if they dont contain your own private markup.

also is fixed hiding of some points, so check it please on your map if it works correctly

points no longer disappear... problem seems fixed. also mailed a log with an apparently bogus rmap.

3) "slow" start: like 2) but loading the maps takes a very long time (ie 30 seconds) and they scroll by slowly one at a time.

locus does number 3 on the first start after every phone reboot for example. is this correct?

Locus also does this very frequently when starting, even without rebooting the phone. Basically, whenever I do some other things with my phone and then restart Locus, it always rescans the map folder and makes me wait a long long time. Pretty annoying, especially since scanning just one single big rmap file can take over five seconds (Galaxy Note with a bunch of 3GB rmap files).

Whatever you cache when scanning map files... is not stored properly.

I thought Locus puts up a requester now for bogus maps. I have seen that once and deleted the offending map. No more requesters appear now, so all maps should work. I can also see them all in the personal maps list.

Locus re-starts in three different ways for me:

1) immediate restore from background, just the same as if the app wasnt quit at all. Makes sense.

2) "quick" start: the "loading... restoring previous state..." window with all the maps and tracks and whatever appears but scrolls through very quickly (ie in less than a second).

3) "slow" start: like 2) but loading the maps takes a very long time (ie 30 seconds) and they scroll by slowly one at a time.

locus does number 3 on the first start after every phone reboot for example. is this correct?

emailed a smaller map to reproduce the problem.

Btw... locus keeps re-scanning my maps folder over and over again on startup, resulting in very long startup times. When quitting and restarting right away, its blazingly fast. But after a reboot or after using other apps for a while, the whole dir is rescanned. Shouldnt the state be cached somewhere in a persistant file? Seems to me its only cached "in memory" and lost very often.

how about a new testing version? and do you still want logs then for those disappearing points? i doubt they'd show calculation result problems.

Log with crashing during a record contain some weird error, that Locus want to notify about GPS state (by sound) and cannot. There were no reason for this, so I at least added some protection against crash of whole app

I changed mobile phones and ROMs inbetween and restored a Locus backup, so maybe that crash is related to a configured sound file not being found anymore.

I fail to reproduce it with smaller maps atm. But didnt I send you MIX200-EuropeSouth.rmap already at one point? Anyway, I am emailing two videos showing the problem. Will see if I can make a logcat thingy as well.

The random crashes were unrelated to the waypoint problem.

I've also had 2.7.2.7 crash randomly twice now while simply running in background recording tracks. That has never happened before. Crashlogs sent by email.

2.7.2.7 behaves strange with a point database of mountain huts and my map called MIX200-EuropaSüd (huge 1.8GB 1:200k rmap of europe, max zoom level is 12). The huts are visible nicely at 10|100%, 11|100% and 12|100% but DISAPPEAR on anything closer than 12|130%.  They also disappear randomly at 12|100% when simply scrolling through the map.

Can also reproduce that problem with another big RMAP (3.8GB 1:50.000 EasternAlpsComplete). Points disappear randomly when scrolling or zooming.

Problem doesnt seem to happen on mapsforge vector maps.

I'd still prefer something on the main screen:
https://getsatisfaction.com/locus/topic ... t_approach

But if you really will not ever render any data on the main screen in a visible way, at least think about an option to auto-show a custom-screen when moving and auto-hide it when stopped.