Messages

Hello tramp,
thanks, nice bug. Will be fixed in next version. Till then I may only suggest to logout and login over top "three dot" menu.

Zdravím, rozumím ale tohle bohužel zatím neumím vyřešit. Obrys se totiž kreslí tak, že se kreslí normální čára obrysovou barvou jen o něco silnější a přes ní se pak kreslí ta chtěná základní čára. Takže jsou to dvě čáry na sobě a pokud by obě měli průsvitnost, základní čára bude a) méně průsvitná díky obrysu pod ní, b) se zcela jinou barvou díky míchání barev. Prekérka ...

Heh díky (i za testování). Takhle pozdě na výlety většinou nechodím, nicméně snad opraveno i to po-půlnoční hlášení, díky.

Tak naštěstí je tam celkem dobře funkční zpět/vpřed.

Nicméně tohle mám v plánu brzy předělat a to tří-tečkové menu zrušit. Nejste jediní kdo s ním má probléby

[@lor74cas]

Hi guys,
two days spend on problems with app install & license over Google Play and the problem with Geocaching Live API on 4.x devices, nice. Both issues out of Locus Map.

I will today publish new Beta version 3.34.3.5 and tomorrow, please excuse me on 12 days (hike in Albania). Not sure, how much I'll have access to the internet, we will see ...

If you will have usage for Locus Map during these days, please use this Beta. Completely new system for login into Locus Store, completely new small "toasts" system (that will hopefully satisfy Google requirements), test support for WMTS maps (temporary caching like for WMS maps only), new main Live tracking screen and some smaller changes ... testing is definitely needed .

Have a nice summertime!

Btw. I'm leaving tomorrow after launch, so if in Beta will be any serious problem, I'll be still able to create new version in the morning.

@lor74cas
quite a big idea to be true ...

@Condor
visible "own icon" on the map is because of "Show my last send location" settings in Live tracking profile.

Problem with POI Alert .. I've improved it little bit, so next version.

Alex, sorry for a complication.
Please read our post here: http://help.locusmap.eu/topic/problem-with-locus-map-pro-initialization-at-startup

Time-based chart does not help here because trackpoints that create a chart simply miss HR values.
I made a little different change, so HR value is used for future trackpoints. 10 seconds was not enough, so I've set 60 seconds range. This means that HR value will be used for up to 60 seconds for next following trackpoints (or shorter if new fresh HR value appear).

The result is useful I believe



An even better solution should be to detect next HR value, interpolate values between and also do not use this HR value for next trackpoints if this is last HR value in the recording. Anyway, for now, current solution have to be enough. So next version ...

Ah thanks, I've updated the first post and hope it is ok for you @develar, that I pointed users directly on your web server.

[@develar]

@develar
firstly, really nice work. I'm sure, many users appreciate it.

Just published version 0.7 of GH add-on.
Main change: using latest stable GH API 0.10

Zkus plánovač > pravé menu > nahoře trošku tajné nastavení > rychlé kreslení (nebo jak je to tam česky).

[*** Version 3.31.3 ***]

*** Version 3.31.3 ***
bug-fix version with minor changes and fixes. Thanks for reports!

[@Žajdlík Josef]

Hi,
issue with route planner ( http://help.locusmap.eu/topic/you-can-not-select-the-drawing-mode-in-the-route-planner#comment-58800 ) will be fixed in next version.

@Žajdlík Josef
usually I need a log, but in this case, I probably see the reason of this issue ... next version.

@Condor
have to try it more carefully tomorrow (issue with screen on/off, weird). Problem with Store is known to me, just not yet fixed ..

Good day alklecks,
this is little un-usuall use case. Sensors in watches usually (for now "always" as I know) does not use common communication with a phone like do any specialized "heart rate monitors" or "barometric sensors". So it is little complicated to send such data from watches to the mobile device (Locus).
So for now, this is not planned.

[@Christian]

@Christian
thanks for a nice feedback. Cannot say that I have a solution for this, but I'll definitely keep this in my mind.

@Žajdlík Josef
interesting problem. Partially unsolvable, but I've at least bit improved it so timeout should be now closer to what you have defined in settings. If you do a tiny touch (movement) on your screen it will reset devices counter and will work as expected. Anyway ... improved.

@Condor
altitude correction is applied immediately when Locus Map receive a new location. Modified altitude may be seen for example in satellite screen or in the top toolbar.

@slarti76
don't know why, but I'm still unable to simulate your issue in track editor. Video record https://play.google.com/store/apps/details?id=com.hecorat.screenrecorder.free ? Thanks

ohgood, thanks, you are correct with tap on map. Will be fixed in next version.
What you mean by left/right panning? When you "tap and hold" on the map, you are not able to switch to right "statistics" tab?