calculate remaining elevation returns "noTrk"

[emariu]

Hello Falco, do you have new version ready with all examples ready and working?

[Falcosc]

Newer version with braking changes is ready and untestet, but all existing tasker projekts have to be reconfigured because the current version doesn't use the correct tasker api, thats the braking change.

After I did test it by my self it will be deliverd to everyone. I will remove the Beta suffix from the app name during this step to tell everybody that you can start to spend time on tasker projekt configuration.

[emariu]

Great news.I'll be waiting for you to test and post also all the new tasker tasks you had told me about

Thanks,Marius

On Thursday, November 1, 2018 11:11 AM, Falcosc <notifications@github.com> wrote:

Newer version with braking changes is ready and untestet, but all existing tasker projekts have to be reconfigured because the current version doesn't use the correct tasker api.After I did test it by my self it will be deliverd to everyone.— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[Falcosc]

The new version is online. I did implement automatic navigation track selection and did remove manual track selection.

And I did mention planed examples. https://github.com/Falcosc/locus-addon-tasker/wiki/Examples

Do you still need screenshots how to import Tasker configurations?

[emariu]

Hello,I did import again the scene and the profile, but now after opening dashboard and I am in a navigation in locus...  the overlay is saying no TRK what am I doing wrong? there is a navigation track

On Wednesday, November 7, 2018 9:34 AM, Falcosc <notifications@github.com> wrote:

The new version is online. I did implement automatic navigation track selection and did remove manual track selection.And I did mention planed examples. https://github.com/Falcosc/locus-addon-tasker/wiki/ExamplesDo you still need screenshots how to import Tasker configurations?— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[Falcosc]

A Navigation track is an overlay over your GPS Track, which got automatically created after you start

• guiding to target
• track to target
• or navigate to target

I did figure out that Locus Map Free doen't create a navigation track which means 3 problems:

1. the dashboard can't automatically find your track, you need to manually tell the plugin which track was selected
2. I did just remove this manual selection feature because you don't need it with locus pro because locus pro creates an invisible navigation track with track id "00000001" which means I have to get the deleted feature back and I need to extent the "look for track 0000001" logic with an exception for locus map free users
3. the missing naviation track does reduce the elevation accuracy. For example if your track does only have 50 points the naviagion track on top of your track generates a track with maybe 200 points to get more consistent statistics.

I did delete the manual track selection because if you navigate a 50 points track, locus pro tells you to go on a very detailed 200 points track. Which means 3 of 4 points are not matching to the selected track and this result into many missed track point information because I compare the next navigation track with the track selection. You can't just calculate and search for the nearest point because this will result into wrong point selections if your track has loops. This meens the only correct and fast calculation is "Match next navigation point exaclty to track point" and this logic will fail 150 of 200 times in this example and will tell you "offTrack" as error. I hope locus map free does use the low detailed 50 point track because the 200 point track is invisible for me on locus free "noTrack" tells that it can't find the high detailed "navigation" track. If Locus free use internal the high detailed 200 point track, locus free users are screewed because the elevation display is useless if it does tell 150 of 200 times that there was no track point found.

Here a locus pro screenshot where I tap on the track during guiding, locus shows me my track and the navigation overlay. And on locus map free I don't have the navigation entry there.

[Falcosc]

@emariu do you have locus map free? I do think about disabling remainig track calculation for locus free users because the manual track selection would confuse locus map pro users. Well, I don't even know which functions are available on free because I can't test with locus free because only with locus pro you have GPS simulation features to test things :(

I could be that locus free is missing the navigation track just because I did start a navigation without GPS signal (because I can't simulate a signal without locus pro) That means I am not sure if my assumtion "locus free doesn't have navigation track 0000001" is correct.

[emariu]

I have Locus pro , not free

On Friday, November 9, 2018 10:28 AM, Falcosc <notifications@github.com> wrote:

@emariu do you have locus map free? I do think about disabling remainig track calculation for locus free users because the manual track selection would confuse locus map pro users. Well, I don't even know which functions are available on free because I can't test with locus free because only with locus pro you have GPS simulation features to test things :(— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[Falcosc]

Thats very good and meens that I could fix it more easily after we found out how to reproduce your device config.

Try to tap on your track edges during navigation and make a screenshot. You have may found a way to disable the navigation track.

Normaly you can even see that there are 2 tracks on top of each other, because of different track point count the arrows are missaligned and you can acutally see that locus pro creates a track over the track:

@emariu do you have the "Navigation" track?

[emariu]

how can I debug the profile imported in tasker on my phone?I tried also with guide on to a target and the same happened No TrkAnd I do not see the second track generated on top of my go to track, just one 

On Friday, November 9, 2018 10:40 AM, Falcosc <notifications@github.com> wrote:

You can even see that there are 2 tracks on top of each other, because of different track point count the errors are missaligned and you can acutally see that locus pro creates a track over the track:— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[Falcosc]

You can manually execute the tasker task in tasker (works even if locus is in background), but the NoTrack error tells you that the addon can't find the "Navigation" track. Which makes sense if you can't find it either on your locus ui. You could just create a task where you just alert->flash the calc elevation result to test when you get noTrack and when it finds your 00000001 track.

Please could you make a screenshot before you tap on the track line and a screenshot after you did touches on the track line? Do short touches. Maybe I could see how you did get a working navigation on "my track" without "navigation" track.

At least I was able to reproduce this behavor on locus free and I belive it's possible to setup locus pro to skip the navigation track as well.

[emariu]

What I observed is.. if I click on any recorded track(or imported track) then it is selected and the pop-up with normal information appears(see last picture) , but if I do a normal navigate to.. a target  then if I try to clickon the navigation track.. then it is not selected and this menu is appearing..(see in ther first 2-3 pictures)

On Friday, November 9, 2018 11:29 AM, Falcosc <notifications@github.com> wrote:

You can manually execute the tasker task, but the NoTrack error tells you that the addon can't find the "Navigation" track. Which makes sense if you can't find it either on your locus ui.Please could you make a screenshot before you tap on the track line and a screenshot after you did touches on the track line? Do short touches.Maybe I could see how you did get a working navigation on "my track" without "navigation" track.— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[emariu]

[Falcosc]

Thank you, I found one missing usecase

"Navigation without GPX file" doesn't work on my device like you did told me. Maybe I could implement this automatically because track infos does have elevation values.

[emariu]

OK please do that..

[Falcosc]

OK, I have to add manual track selection.

"Navigation with GPX Track" is available as 10000001 (constant value, usable for automation "Navigation without GPX" is available as "87" if you have 86 tracks in database and api don't tell me that you do follow 87 or 86 ore any other track, which means you have manually select :(

[Falcosc]

@emariu Would it be ok for you to manuall select it or should I ask for an API update and wait for response?

Manual Track selection work like this:

• click track line
• click information
• click the share icon
• select a new menu entry "set track as active"

[emariu]

I think you should do both.. First implement manual selection and in the mean time talk to Menion to update API :)  On Friday, November 9, 2018, 1:27:45 PM GMT+2, Falcosc notifications@github.com wrote:

@emariu Would it be ok for you to manuall select it or should I ask for an API update and wait for response?

Manual Track selection work like this:

• click track line
• click information
• click the share icon
• select a new menu entry "set track as active"

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[Falcosc]

@emariu please try it: https://play.google.com/apps/testing/falcosc.locus.addon.tasker

does work well for me.

If you got noTrk or offTrk results you need to manually select the correct track

1. click navigation track line
2. click information
3. click the share icon
4. select a new menu entry "set to active"

[Falcosc]

@emariu here it is - collecting votes: http://help.locusmap.eu/topic/add-guiding-track-id-to-api

[emariu]

Hello.. tried again and also I had No Trk ..so I manually selected the track and then finally I got result remaining altitude :)
The problem is that next time I use Locus and try a new navigation to another point.. I did not manually select the new track and it automatically showed the last elevation remaining to the last target(old value) If I manually select the new track again, then the overlay is showing the same OLD value not the new one I clicked on the overlay to make it disappear and selected again the new track and after 2 minuters the new overlay had the correct value

[emariu]

as a mention, your add-on got automatically updated on my phone from google play an hour ago.. I hope it is the latest version?! Please make the version numbers visible when I open your add-on application from my phone, to check if it is correct version

[Falcosc]

You should trigger a recalculation on your dashboard button because the example profile is executed every 2 minutes. Or generate an app icon for manual recalculation.

Do you have hardware buttons to spare? For example I have a camera button with half press. I use half press to switch display brightness low/middle/max and full press does change between dashboard and map. I do call the overlay update on each full press and get new calculation everytime I switch to dashboard.

Or make a Task "display remaining elevation", convert it to app and add the converted app to your locus panel, like this: https://github.com/Falcosc/locus-addon-tasker/wiki/Custom-Task-Icon-at-Locus-Panel

Version number should be part of Play store or app info screen (long click on app icon if your launcher does support it)

Automatic track selection does only work during guiding or navigation based on existing track.

Do you understand why the switch from old navigation to new navigation doesn't work with your setup? The addon does have all the needed data you just need to collect it with tasker.

And did you understand when the navigation track could get automatically selected and when you get a noTrk error?

It's a little bit difficult to allign the overlay because you only have move left and move up in the "show scene" action of the task.

[Falcosc]

And thank you for testing with your device, too. I did move the beta version to release now. Don't be affraid to stay on beta track, I do actually test my app before beta phase.

[emariu]

I see now that I'm on version 1.0.3 What program do you use to map a hardware button to changing between dashboard and map? Teach me how to do it,please. Also I need some help with setting up the scene overlay. What settings do you have? I have 1000x350 geometry,but the overlay and numbers are too big and taking much space of the map display

[emariu]

Can you please make the overlay transparent? To see more of map content through...

[Falcosc]

You can change the overlay settings in screen tab. But positioning have to be done in task. Scene design belongs to scene config and positioniing is part of task "show scene".

I use "Autoinput" Tasker Plugin to assign any hardware button id which is available on my phone to my profile trigger. If you don't know the name of the button you can manually enter the button by pressing it in the autoinput key select dialog.

Toggle Dialog is a little bit more complicated. You have to create a locus settings preset with dashboard and a settings profile without dashboard. Then you can create a task which select dashboard preset or non dashboard preset. Locus Tasker Plugin "Execute Action" could then do the "Set Preset" Action to apply it.

I can't export locus presets, which means you have to create them by your own. Maybe I do share some screenshots about this topic because I'm a little bit proud of all my hardware button tasks for brightness and dashboard management.

Would be nice if you could share any ideas for usefull Locus tools to make this great app even more versatile. Even if you can't setup them in tasker, it would be nice to know. Things like dashboard buttons will never be a nativ solution in locus because this would require way to much configuration layouts and that is the point where tasker is the better tool because they did fokus on configurable interactions.