Quote from: menion on March 15, 2019, 16:43:51
Last Beta version 3.36.2.13 published.
I am not able to do anything groundspeak related with this version.
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 MenuQuote from: menion on March 15, 2019, 16:43:51
Last Beta version 3.36.2.13 published.
Quote from: menion on February 27, 2019, 14:02:02
@john_percy, @Spartaner
the issue will be fixed in the next version. I've found a method how to specify where will be SVG images cached. So I've set Locus internal directory which is cleaned after app closes. Believe it will be good enough.
locus.sv@heime.org
hehe oki, but then I'm still unable to simulate it. If in your third step, I choose different cache, app firstly sends this "found" log, then tries to send trackable log and that's all. After closing first error with cancel, no additional "log found it" for the cache is send.
Ah maybe I see it ... you pressed "retry" when this error in logging trackable happen right? Hmm oki, I've fixed it now, hopefully. Thanks.
Quote from: menion on February 27, 2019, 09:00:52
@locus.sv@heime.org
ah ok, so you made some changes directly on the web page. Then what happens in Locus is partially correct in the current system, when Locus use the list of trackables used in the previous log (as do now) without loading always fresh list. I may change this and always load the list of all available trackables ... but does it worth it? It will prevent this error but slow down a little logging system because it will need to download the whole list from gc.com.
Quote from: menion on February 26, 2019, 15:19:41
Sorry, but I'm still unable to simulate something like this. May you please write me some steps to follow to simulate this error? I mainly do not know how to get to state when "The Locus inventory list then contain trackables which is not in my Groundspeak inventory".
Quote from: menion on February 25, 2019, 19:17:49
@locus.sv@heime.org
Locus can't know if there were meanwhile any change in your inventory. That's why it always needs to reload your current fresh data. A big problem in the field? If so, then it may be better to log "visited" in batch over "Logs manager".
And to problem in second post. How did you do that "log a trackable as visited which is not in my posession"?
Quote from: menion on February 19, 2019, 22:31:48
@locus.sv@heime.org
ah, this helps (two screenshots), thanks! Seems that all trackable logs now needs a text message wrote by user. Not sure why I did not notice before. Anyway, it complicates UI a lot for quick "visited" and "dropped off" logs. Can you (or other active geocachers, @balloni55) imagine some automatic text always inserted into these quick logs?
Like simply for "visited" log insert "visited" and for "dropped off" insert "dropped off"? I know, you will want to configure these texts ... later.
The second error is also nice, seems even a geocaching server had some problems with it. Why this happens is not clear to me. Did you tried to send the same log again or was this done by Locus itself automatically?
Log trackables from "Logs manager": I've found this as well and also found an issue here with logging. Fixed, thanks.