Messages

Ich habe gerade mal getestet, funtioniert ohne Probleme 

New subscription with LoCoins yesterday, it just all worked flawlessly, was a matter of 10 seconds.

Yes, I added deactivated entries. Longtap -> Screenshot.

Ah, I looked at %guide_navpoint1_time, it seems to be remaining time in ms, you're right.

Often you rather get a unix timestamp and calculate the difference. You probably know you can do maths in Variable Set actions.

"It goes day and night" - it's up to you to define when it runs. You could add an additional variable context, make it run only eg if "%IAmOutside=true", you could control the profile through other tasks - there's an action "Profile status" which turns profiles off/on. You could add a time context. Whatever you wish.

See in my attachment how a profile is tamed by multiple conditions. Often I have to let the entry task start, but if certain other conditions are not met, I will stop it (via the Stop action) as soon as possible.

To your profile, I have added the condition of Locus being on top, just an idea.

Freischneider, I have changed your profile to use Tick. As for the times returned by the plugin, those are always in unix seconds since 1970..., a big number. The current time is in %TIMES. You can use the flash action and look yourself.

I have added flash, 2 plugin independent zoom intents and the tick set as disabled code on top of your task, for your inspiration. It runs only if Locus on top.

https://taskernet.com/shares/?user=AS35m8kdDIMDeveQcQfRglam%2Fah1mTW%2FWcg05FZ39c0i1q%2F77iY3E7cIwxCkXqJTaTA%3D&id=Profile%3ADistanz

Hallo Leute, bitte denkt daran, dass die "Voreinstellung" keinen "aktiven" Status hat. Wenn Sie auf eine "Voreinstellung" tippen, wenden Sie nur eine Reihe von vordefinierten Einstellungen an und das ist alles. Die Voreinstellung ist nicht aktiv und alle Änderungen in den App-Einstellungen haben keine Auswirkungen auf die zuletzt verwendete Voreinstellung. "Voreinstellung" = einfach schnell mehrere Einstellungen auf einmal ändern, mehr nicht.

Hello Menion,

once again on this topic. I had some time to look into it over the weekend and found some inconsistencies and, in my opinion, a bug.

First of all, thanks for the update 4.15.2 (impoved computation of uphill/downhill distance) - this is more realistic now.

I am still not completely happy with the new calculation of the elevations. In my opinion, ignoring elevation differences of up to 5 metres is too strict. In relatively flat regions such as Berlin and the surrounding area, too many actually existing inclines and declines are calculated out, and the result is then not very realistic. If I go on a cycling or jogging tour and have several short but distinctive inclines, which clearly require effort when running and can also be seen in the altitude graph, and the result then shows 0 metres of altitude, this is not ideal. 

In addition, there are sometimes strange results that make no sense from a purely mathematical point of view: A recorded track shows "Min altitude" 30 m, "Max. altitude" 66 m (a difference of 36 m), but only 30 m elevation gain is displayed. (Screenshot 1 and 2.) So 6 metres of altitude are "swallowed".

Then I noticed a faulty behaviour in the Track Analyzer, which might be a bug. A track section selected with the analyzer always shows exactly the same value for elevation gain and loss, even if it only goes uphill or downhill (screenshot 3 and 4). This can be reproduced everywhere.

(it's not even possible to multi-select and delete trackpoints!)

... or to embed multiple waypoints into a track at once.

I would like to add Management of Track Waypoints as No. 5.

Yes, please don't forget about this. There's a bunch of improvements needed here, many very basic (it's not even possible to multi-select and delete trackpoints!)

Thank you Menion.

I would like to add Management of Track Waypoints as No. 5.

As for now, when I plan my hiking trips, I use embedded waypoints, so that the track file is able to be sent to my trekking partner as a complete KML file. These embedded waypoints can't be managed properly. I would like to be able to search for them, display them in a certain radius around the cursor etc.

So my workaround is saving every embedded waypoint twice – within the track and as a "standalone" version in my points folder. This is more work for me, but also raises problems, like when I edit a point in the points folder, it doesn't change in the corresponding track and vice versa.

A second thing would be the improvement of data sharing (e.g. via shared folder).

Best, Lucas

Hi guys, nice bunch of ideas, thanks. So when I noted and analyzed all, seems that we have here four major categories

• better work with online/offline LoPoints
• robust search system
• dashboard improvements
• geocaching features

Where
2. search system is currently (already for a few months) in massive rework. During the next week or two will be in Beta a completely new online search. More about it later ...

LoPoints & Dashboard are very high on my priority list, so definitely something I would like to work on this year.

And geocaching ... good question. Will have to think a little more.

---

Other smaller tasks
- backup system: agree, I'll look at it soon
- 3D maps: huge amount of work that still does not worth it I believe
- recording statistics: I would love to see them too, but we are not the majority
- live tracking: I know, sorry @joeloc. This has to start with a rework of our old server and uniting it to a new web.locusmap.app site. I'll try to push it a little more.

Anything else serious?

The Lopoints system of temporary points. Awkward handling, allow predefine sets of categories etc.

Hi, ah I see. It is a problem on our server that does not send Gold subs item in case, user does not have enough LoCoins, we will fix it, thanks.

The system of backups needs to recreate.... I need to find a time (week or rather too)...

If you work on it please add no-go area,too.

The system of backups needs to recreate. I wrote about it a few days ago (again). So use it as is. I need to find a time (week or rather too) and unite "settings" + "full" backups into a single system with options ...