This object is in archive!
only 2 lines of each log-entry shown in geocache-logs !?
Solved
Since last update i cant see the complete logs of a geocache.
Only 2 lines are shown of each log entry and "press-and-hold" on them opens the web-page "translate.google.com" ...
The problem is not located in the imported PQ. Imported same PQ in NeonGeo and everything is OK.
Is there an option to de-/activate the "full" logs?
The same problem 
Hi Rudiger,
seems to be problem on Android 2.X version. Thank you for the report. Problem is now fixed and will be fine in next release
Hi Rudiger,
seems to be problem on Android 2.X version. Thank you for the report. Problem is now fixed and will be fine in next release
I have that problem too. Android 2.2, so of course.
But...
Long ago I noticed, that Locus was very slow to load GPX files with 10 logs per cache, so I changed my GPX files so that all log texts are in a single log entry (per geocache).
This made GPX loading a lot faster.
Now I tried it again with separate log entry for each log and I think Locus is still slow.
Is it necessary to parse each entry when the GPX file is loaded into database?
It would be much more efficient to load the logs ({groundspeak:logs}) element as a single entity. And only when the user is viewing the logs for a cache, then each {groundspeak:log} element needs to be parsed.
All the above is IMHO. What is Menion`s HO?
I have that problem too. Android 2.2, so of course.
But...
Long ago I noticed, that Locus was very slow to load GPX files with 10 logs per cache, so I changed my GPX files so that all log texts are in a single log entry (per geocache).
This made GPX loading a lot faster.
Now I tried it again with separate log entry for each log and I think Locus is still slow.
Is it necessary to parse each entry when the GPX file is loaded into database?
It would be much more efficient to load the logs ({groundspeak:logs}) element as a single entity. And only when the user is viewing the logs for a cache, then each {groundspeak:log} element needs to be parsed.
All the above is IMHO. What is Menion`s HO?
IMHO, HO, crazy shortcuts :)
I`m currently testing import. By default 78sec. Then I disabled in code checking for duplicate logs and merging old data and result is 72sec, so it`s not really a problem I think. Shouldn`t there be different thing that slow down import? Btw. what you mean by "slow"?
Anyway I don`t see any other solution. XML content that have cache data, needs to be parsed completely. There isn`t possibility to parse only a part. Sorry
IMHO, HO, crazy shortcuts :)
I`m currently testing import. By default 78sec. Then I disabled in code checking for duplicate logs and merging old data and result is 72sec, so it`s not really a problem I think. Shouldn`t there be different thing that slow down import? Btw. what you mean by "slow"?
Anyway I don`t see any other solution. XML content that have cache data, needs to be parsed completely. There isn`t possibility to parse only a part. Sorry
All right!
I`ll try loading individual logs for all GPX-files.
But I still think that it would be possible to store
{groundspeak:logs}...{/groundspeak:logs} as a single entity into Locus database.
Only when the user want to see the logs, there is a need to parse it further.
But again, just In My Humble Opinion.
Slow?:
About a year ago I tried to load max. 10 logs with each cache. Then it was definitely slow; 2...5 times slower than with a single (but long) log.
All right!
I`ll try loading individual logs for all GPX-files.
But I still think that it would be possible to store
{groundspeak:logs}...{/groundspeak:logs} as a single entity into Locus database.
Only when the user want to see the logs, there is a need to parse it further.
But again, just In My Humble Opinion.
Slow?:
About a year ago I tried to load max. 10 logs with each cache. Then it was definitely slow; 2...5 times slower than with a single (but long) log.
stebu what are you trying to do? You`re loading GPX file with caches directly to display on map or you`re talking about import to database? Because I`m still testing import. I did some tests and seems to works correctly, nothing new what should block progress and slow down import.
Speed of import is also affected by you card, so in internal memory it will be for sure faster then on slow external SD card.
stebu what are you trying to do? You`re loading GPX file with caches directly to display on map or you`re talking about import to database? Because I`m still testing import. I did some tests and seems to works correctly, nothing new what should block progress and slow down import.
Speed of import is also affected by you card, so in internal memory it will be for sure faster then on slow external SD card.
Hi, I updated yesterday to Version 2.20 and now I can see only two lines of the logs like it is posted here. I use Android 2.3. The complete log is still present and I can read it by copy to an other App. Is this the same problem than before or is there any possibility to make the logs visible? Thanks for this world best Geocaching App!
Hi, I updated yesterday to Version 2.20 and now I can see only two lines of the logs like it is posted here. I use Android 2.3. The complete log is still present and I can read it by copy to an other App. Is this the same problem than before or is there any possibility to make the logs visible? Thanks for this world best Geocaching App!
Hello, ah yes, it may be same problem. I changed a way, how these logs
are displayed and probably same issue (it's in Android btw.) appear.
It should be anyway fixed now, so if you want to be sure, you may test this Locus test version
Hello, ah yes, it may be same problem. I changed a way, how these logs
are displayed and probably same issue (it's in Android btw.) appear.
It should be anyway fixed now, so if you want to be sure, you may test this Locus test version
Hi Menion, I install now the test version 2.20.2 and it works! The complete logs are now visible. Thank you for this fast response!
Hi Menion, I install now the test version 2.20.2 and it works! The complete logs are now visible. Thank you for this fast response!
Perfect, thanks for confirmation
Perfect, thanks for confirmation
Replies have been locked on this page!