Messages

Locus Pro, version 1.4.0

The new guiding command "Nearest" incorrectly forces Guiding On Reverse back to Guiding On.

How to recreate the problem:
  - Create a track (straigt lines) with some few points.
  - Select Guide On Reverse.
  - Move map center closer to another point on the track but with a distance > Guiding/"Set next point".
  - Tap the new command "Nearest". Guiding correctly selects the new track point.
  - Next step goes wrong: move map center closer than Guiding/"Set next point". Guiding incorrectly jumps FORWARD to the next point as if Guiding On were active. It should jump BACK since Guiding On Reverse is active.

If you do not use the "Nearest" command, the Guide On Reverse jumps correctly backward on the track as you get within the Guiding/"Set next point" distance. So it is clear that it is the "Nearest" command that forces the guiding to normal (Guide On).

How great! I am glad this was so easy for you to implement. Thank you!

That is certainly a very useful command when you pass a point without jumping and you want the guiding to reselect the closest point. And that is for sure an important command to offer.

However, this doesn't cover the case when you pass a point at a distance too far to make it automatically jump to the next point. You know that you are finished with that point even though you passed at a far distance, and now you want the guiding to guide you to the next point on your track. In this case your new "Nearest" command will only pick the same point again and again until you are halfway to the next point. So I would think we need both your "Nearest" command and my requested "Next" command. Hope you find this meaningful too. Thank you.

The guiding line shows the distance and azimuth to the next point. So then time had to be to that same point. Anything else would be confusing in my opinion (distance to guided point while time to end of track - no, that wouldn't make sense to me). Since all three items (distance, azimuth, time) are shown together in the Title field, then they all have to refer to the same point. That is why I thought this was almost there already, but if it requires a lot of effort, put this at lowest priority.

I looked through the sort results once again, but I can't see any pattern. There is a small difference from test version 1.3.0.3, now getting this sequence:
  27/3, 20/3, 18/3, 17/3, ..., 15/3, 14/3, 12/3, 8/3, 7/3, 28/2, 1/3, 2/3, 3/3, ..., 7/3,
Compared with 1.3.0.3 some dates moved from the trailing end to the top, but still there is this strange sequence with descending dates down to 28/2, then changing to ascending dates. This is particularly strange since your normal sorting is correct. It has nothing to do with change of month, because I have a new track from 4/4, and that one is listed at the correct place.

I did a quick test with version 1.3.0.4. Same error. I look more into this tomorrow to see if I can find a pattern.

In test version 1.3.0.4 this works perfectly! Thanks!

I discovered today a Waypoint guiding feature I was not aware of: Selecting "Guiding" in the Title field displays distance, bearing and estimated TIME to the waypoint. Track guiding doesn't display the time. Would that be possible? I imagine you have all required info and features there already, it is just a question of displayng it for Track guiding too.

I have been testing test release 1.3.0.3 with track guiding on two run exercises today  and realized the following issue (should be an easy fix):

If I am following a created track with guiding turned on, the guiding automatically jumps nicely to the next point when I am within Guiding/"Set next point" of the current point being guided to. Works really great in release 1.3.0.3.

But the issue is when I find it appropriate to pass the current guide point at a distance > "Set next point" value. Then the guiding will never give up the current point. Only way to make it jump to the next point is either to enter a higher "Set next point" value to trigger the jump, and then change back again, or to turn guiding off/on when the next point becomes the closer of the two points. Neither works very well.

So what would be really useful is this:
- if you tap the track (a point on the track), you get a pop-up menu with 3 commands today: "i", "Chart", "Guide Off". Add a new command here - "Next point", which will force the guiding to jump to the next point. I would think that should be very easy to implement, since all functionality is there today. The only thing needed is to let this command force a trigger of the "Set next point" condition.

It doesn't work as you describe.

I set "Set next point" = 100. Even if I am several hundred meters away from a point, but that point is the closest one to map center, then turning guiding on always selects the NEXT point on the track. There is no way I can make it select the closest point. I also tried with map center far away back from the first point on the track (so the track was going away from map center). Even then it picked the second point when I turn on guiding.

BTW: I like very much your new "Guide On Reverse". That is very useful if you want to travel the opposite way, e.g. you want to follow the track back to your starting point. Great feature!

Tested with 1.3.0.3.

Works great! Very useful and great features! This must be classified as 100% perfect!

From what has been discussed on the forum recently, seems you have implemented all the features people have requested.

Thanks a lot!

Installed 1.3.0.3 and tested.
I like your Reverse Order implementation!

I have 35 recorded tracks, and tested your reverse sorting feature. Here are my test results:
- normal order sorting is correct for all sort criteria (by name, create date, etc).
- reverse order sorting is correct for all sort criteria EXCEPT for 'Create Date'. In that case I get an order that makes no sense:
   I get the following order of my tracks (they are all in the same category - 'recorded') when sorted reversed by Create Date:
     14/3, 12/3, 8/3, 7/3, 28/2, 1/3, 2/3, 3/3, ..., 7/3, 27/3, 20/3, 18/3, 17/3, ..., 15/3
   I get the same result if I reverse the sorting back and forth, so it is consistent. They are sorted correctly if sorted normally (not reversed).

 Hope this can help you identify the problem.

You ask me to try, but there is not such menu entry. Is this a new feature in a version you haven't released yet?

You are referring to a setting called "Beep when you move too far from track". Can't find anything like that in any menu. Is this a new menu entry in a version you have not released yet?

What I noticed is that I got the beep EXACTLY at the same time as the guiding jumped to the next point on the track. Every time. I think I checked about 15 points.  That is fine, I just interpreted the menues differently. So the "Distance for sounds" is only for guiding to one point  and is not used when guiding on a track? Ok, that's fine. Should mention that I create the track with straight lines between the points (i.e. after selecting the track points, I save the track without selcting "Compute Route".

I also tried to pass the point by much more that the distance settings and never got any beep for gone too far (related to the missing menu entry mentioned above?)

I noticed the following (GPS is off):
- I place map center (red cross) close to one point and turn on guiding. The guiding then does not select the closest point, but the NEXT point on the track. Did several tests with different tracks and different point with different distances. Same result every time.