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.

Messages - menion

Pages: [1] 2 3 ... 707
Versions / Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
« on: February 21, 2019, 09:49:37 »
hmm between step1 and step6 is only 200 ms! So in creating UI won't be a problem. Your log is full of some information about "FwkPlugin". Not sure what is it but seems it may slow down the display of the screen. Anyway "step6" is last moment before screen should be visible, so sorry, I have absolutely no idea what happens here :/.

thanks for the algorithm, I'll look at it.
About the list of tracks: well, I was doing just a tiny improvement not some huge changes.
- scrollable list ... heh sorry, fixed
- problem with "Too many requests". In the app is already defined pause between requests, but seems not to be enough. So next version ...
- logging own cache: I've firstly removed "found" and "not found" option from list of logging options in the case, user is the owner
- delete log in logs manager ... best probably long click on the log and in opened point screen just delete log at top of the screen.

@Andrew Heard
what about mentioned domain? Where you get the info that this page is somehow related to live tracking?
The issue with time ... I'm trying to simulate this issue and still no success. I know about it, but still not found exact steps to reproduce it. Does this happen always for you?

Versions / Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
« on: February 20, 2019, 11:10:30 »
@Andrew Heard
from where comes address?
Just a few days ago we published a new page for live-tracking on: ... it's not yet 100% finished, but most for version 1 is already done (mainly "users guide" is in preparation).

So @all ... if anyone uses LT, feedback is welcome of course :).
hope that duplicate send was made by the problem with trackables. Anyway, even with the current Pro version, it should be possible over logs manager to send twice "found log". Never tried it before :).

I'm mainly curious why this happen. We will have to find it over logs. New beta version now have some error logs ... so try it, create log after you open style editor and then in log, should be few lines with text "createDialog, step..." so extract them or just send me full log, thanks.

And new Beta with few more fixes is out.

Discussion/New features / Re: Can Locus Map compute E5a/L5 signals?
« on: February 20, 2019, 09:44:35 »
Hello pere,
feel free to join our discussion here ;)

Downgrade bez oninstalace opravdu nejde. Nicméně lze použít menu > vice > správce zálohování, udělat zálohu nastavení a po pře-instalování zase obnovit (jen to nastavení stačí pokud je Locus v default adresáři v rootu interní paměti).

Jinak jak se dostat k Betě máme tady:

omluva za chybku, v poslední Betě, pokud potřebuješ novou funkční verzi, to již funguje. Regulérní update bude bohužel až začátkem března. Případně starší verzi: . Díky za pochopení.

Versions / Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
« on: February 19, 2019, 22:31:48 »
this will be complicated :/. Thanks for tracelog, I see there some issue in creating the view, but unfortunately, from this Beta version, it is not clear why this happens. I'll firstly try to ask my colleagues if they won't be able to simulate it. Does same issue happen also with the Pro version? Does this happen before? You are the only one who wrote to me about it.
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.

good point with this notification. Removed, thanks.
I've found that in certain cases, Locus did not marked send trackable log as really send. What happens to you is that Locus Map tries to firstly upload not yet send logs (which were already sent) and then try to load your inventory. Just press left button to throw away this log. Anyway will be fixed in the next version.


Thanks all for testing of this geocaching stuff. As I wrote, Groundspeak decided to completely change it's old API so I had to completely rewrite little-complicated logic around logging & few other stuff in the app. So already quite well-tested system needs to be re-tested again. Appreciate your time, because I know this is a problematic topic for testing mainly because no one wants to spam other caches or trackable.

Do not forget, that in Beta version is possible to enable communication with (in the app expert settings), which is testing copy of original Groundspeak server where everybody may do whatever wants ;). Ideal place for testing.

Versions / Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
« on: February 19, 2019, 14:20:20 »
Version published.

hmm let's try one thing ...
- update to new beta version
- after start, long! click on the main menu icon a in new "Dev menu" click on the "measure method usage". Right after this open any track or Route planner and be ready to just once click on "Line style" to open editor.
- after you will see "Tracking started" (after 10 seconds), just once click on "Line style" to open editor and leave it be until you will see another green toast with "Tracing finished into file ..." (after one minute).
- send me or attach here generated file (placed in root of Locus folder).

Versions / Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
« on: February 18, 2019, 19:20:48 »
@Žajdlík Josef
thanks very much. You have found quite a serious issue in parsing GPX files (that are received from BRouter as well), will be fixed!,
I've found a few issues related to "Forbidden" error > improved. Anyway it's because of some missing info in the request but there is so many combinations ... you have item, somebody other has tb item, it's in some cache where you are now, different cache .. ah ... next version and we will see :). The error message should be now exact text from Groundspeak so hope it tells more if the error appears again.

Problem with the import of PQ, if any, is definitely not related to Geocaching itself. If you download your PQ file and start import manually, the same issue happen? It will be most probably the same issue as I fixed based on Josef feedback (start of this post). So please test the next version.

1. "slow open" > only in Route planner or also in detail of already stored tracks? I see no similar issue. Does it happen also when the route planner is clean, with no track planned yet?
2. hmm, this is most probably correct, good observation. I have a todo list of bigger tasks to improve in Route planner when there will be "Route planner work-time". Even if this does not look, it is a more complicated task. As also @Andrew Heard wrote, it is not a big problem. On the second side, even manually draw long line colored by elevation from HGT should be really useful, so I consider this as something, that should be improved.
3. dialog ... heh, nice, but I tried for a while to find it, but no success so far

really interesting, never saw this problem :/. Will be watching it, so thanks for the report.

Versions / Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
« on: February 16, 2019, 17:23:44 »
Really interesting. These small red arrows usually indicate "via-points".
You use default config for car routing? So Car >Fast, routing profile: Car-FastEco?

Versions / Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
« on: February 16, 2019, 13:45:42 »
Login works, finally :)

Forbidden error: hmm nothing like this happen to me. What should I do exactly to simulate it? If some tracking code needed, send me it over PM, thanks.

And images for trackables ... we may discuss improvements once all existing functionality works as before ;).

Discussion/New features / Update of map core (2019)
« on: February 16, 2019, 13:05:25 »
One of the major problems with maps are caused by really really old system how the app works with map files, online maps, the system for rendering map tiles etc. I decided to update this system to try to solve most of the major problems.

Main info: to test changes is needed special ALPHA version. Currently not yet published, plan is on start of March. Subscribe to receive new information once ALPHA is ready for the test.

Current major visible changes

  • automatic scaling of all raster maps based on device DPI
  • support for custom HDPI online maps, more info

In progress/preparation
  • features related to MapsForge V4 maps, more info

Versions / Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
« on: February 15, 2019, 19:45:06 »
Ah, more complicated then I expected anyway new version published. So third try ...

@balloni55 , I'm worried that Opera browser will be, as usual, causing troubles. So at least for now, try to use any different browser for login, thanks.

Versions / Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
« on: February 15, 2019, 18:11:33 »
Ah thanks guys, got it. I'll prepare one more version with hope. it will finally work ...

Versions / Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
« on: February 15, 2019, 15:32:32 »
@Žajdlík Josef
I believe I've found a reason for your issues and they are solved in Beta ... you confirmed it, perfect.
In Pro, login most probably expired and usually, it is automatically restored, but because of your issue, it does not work anymore. Sorry for this, Beta needed :).

not clear from UI, I know, but the top panel with "Login required" is not clickable. It is the same as in Pro version > just information panel. Login is automatically called at the moment, you use the function that  needs a login, like load of PQ files.
Anyway even here, you see only "loading", hmm. In which browser login opens? Or you see a browser with the same blue top panel as is in Locus (and "Powered by Chrome" visible under top right three-dot menu)?

Versions / Re: [APP] - version 3.36.+ ( 30. 1. 2019 )
« on: February 15, 2019, 12:01:41 »
Finally Groundspeak fixed some problem in setup of Locus Map on their server, so new version published with the second version of login to Geocaching API, so let me know if it works, thanks!

I think that both systems are needed. In config is predefined few methods and you may directly attach hardware buttons to them. Useful for direct support of BT controllers for example. Configuration over API (tasker for example) is a lot more flexible and possibilities are almost unlimited (limited only by what I offer over API), but they need a lot skilled user to setup it properly :).

Pages: [1] 2 3 ... 707