Topics

Hi Menion,

I am getting a regular crash of Locus Pro with one of my pocketquerries. Others just work fine. GSAK opens the troubling compressed GPX without problems though.

Locus fails at either while importing waypoint 285 or 286. I therefore tried to extract this points from the GPX file and import them on their own. But all GPX with just one single waypoint of those import just fine. I really dont see what I can do here, better for you to look why Locus breaks over this one.

WPT 285 should be the one with <wpt lat="50.946933" lon="11.352433">

Cannot upload the file here (4 M). And the extracts seem to work out. Any way to send you the file?

Thanks and best regards

Hi Menion,

with the new update the geocaching api is working for me too Thanks for that.

I have however a few remarks for consideration.

- during logging a cache to fieldnotes one will get the question (online-log, online-fieldnote, offline-fieldnote) each and every time. Would be nice to have a preselection here that is configurable or something.
- the same feature as above, during selection there is no way to abort the process (granted it's not missed that much )
- upload of fieldnotes. Now all entries are unmarked. I would consider all entries marked more useful.

As for the download of pocketquerries. Seems to work fine. I'm still dreaming about some cool way of automation of let's say regular download of pocketquerries to certain well defined poi categories

Best regards

Hi again,

first thanks for the comment in the other thread I accidentally closed it and cannot coment anymore. Now I've got a new strange behavior with it. When finishing the note a new dialog pops up telling, who to proceed with the File, where it is stored and so on. Answers are "yes, send" and "abort". Either way note goes to file. But if choosing the first Locus also tries to connect to some server which fails.

didn't Chance any settings and did bot find a setting to switch that off. What about that?

Best regards

Hi Menion,

I just found some strange behaviour with the Geocaching Fieldnote File. I used a doublequote (") sign in the textmessage of the fieldnote. This however brakes the upload to Geocaching.com without any hint from there... Maybe it would be good not to allow for the input of those characters or parse the string before saving.

Best regards

Hi,

and just once more: thanks for Locus

What do you think of the following idea.
It should be possible to increase zoom level beyond available tiles (in offline mode) by some kind of digital zoom of last available tiles. (Say, if you got level 21 only and increase zoom you end up in the grey) I don't see why this cannot be done, image resolution is not that bad to go at least another one or two levels up. That would certainly increase usability especially if using lots of POIs (such as geocaches). It's not the same as the optional double scaling that is configurable, but active at all zoom levels.

Furthermore I would find it conveniant to be able to increase zoom level without tiles (that is, in the grey) more than one level beyond available tiles. I know one could switch to "blank" map, but thats somewhat bulky to use.

Give it a thought

Thanks and best regards, yahp

Hi,

once more: thanks for Locus!

Do you think it would possible to add a quick toggle button to simply turn of all pois on screen (say in the right panel or so). So press once, show no POI, press again show the POI according to selected categories. Especially useful for crowded POI areas, such as geocaching, where one cannot see anything of the map due to big symbols of the POI.

Just to think about

Thanks and best regards, yahp

Hi there,

first of all: Thanks for Locus!

Now for the problem, at my HTC Incredible and Locus 1.8.7 there is some strange behavoir with the field notes. Actually the don't work anymore. No Fieldnote.txt (whatever the name was) is created, nor do the templates work. One can try to log a cache, but then again no file, no entries and no change of the icon. Any help, suggestions or recommendations are very welcome.

BTW: While it was working I like to suggest, that the template - using {h}:{m} - results in single digit minutes, which just looks stupid (say 19:4, instead of 19:04), perhaps this could be changed too.

Thanks and best regards, Yahp