I've discovered two new "Out and back" bugs.
Bug 1:
1. Press "Out and back"
2. Press Undo
3. Press "Out and back" again. A message appears that says that I have already used the "Out and back" feature once on the track. This is of course not true since I pressed "undo" in between.
Bug 2:
Distance markers are not displayed for the "Out and back"-part of a run while drawing. Once the run is saved the run displays correctly in the future.
Thanks for bringing this to our attention Magnus. I've fixed the "bug 2" that you listed.
As for "bug 1", I think that the functionality here is open to interpreation as to which is 'correct'. In my opinion, the way we do it now is correct, since you have gone out and back already. In any case, I think this is an uncommon scenario, and I'm inclined to leave the functionality as-is unless it's causing specific troubles.
Thank for the quick response on bug 2.
It seems like we do have different opinions on what the undo button does in relation to "Out and back" feature.
My interpretation is that undo simply returns the map to the state it was in just before the operation preceeding the pressing of undo.
Consider this scenario:
1. I create a route on the map.
2. I press the "Out and back" button.
3. Then I realize that "Bummer, I forgot to add that last piece of the route before going back." So I press the Undo button and complete the "Out" part of the run.
In my oppinion, at this point I have not yet used the "Out and back" feature on the map. I have indeed pushed the button once, but the "Back" piece of the route is no longer available on the map.
Enough of ranting. I think this site is one of the most useful that I have come across on the internet, it is truly great. Maybe a bit slow, but that could be because I use IE6.
So if I seem to be nagging you with bug reports it is just because I want to help you nailing the remaining bugs. And indeed, sometimes wether something is a bug or a feature could be a matter of oppinion.
Hi Magnus-
I certainly see your point, and I have looked at it from this perspective. I agree that your interpretation is probably "more right" than the way we're dong it now, but from a code perspective, implementing it this way will add quite a bit more logic and code for a scenario that happens very rarely.
At this point, I would agree that this can be seen as a bug, but a very minor one that we don't plan on fixing in the near future. This frees us to develop new features for you to enjoy.
I have an alternate solution to this issue that should be much easier to implement.
How about having a "delete from here to end" and a "delete from here to start" functions when editing a route. This would allow you to extend a previously saved "out & back" route as your run progresses and it would allow you to change the end or beginning of an out & back run to take little loops or side paths that some people (like me) are wont/apt to do (that's one of the joys of exercising outdoors).
Thanks for the great site!
I was just creating my first map. 75 percent of the way thru I got things a bit fouled up and could not figure out how to remove the offending points. the route was a loop that came back to the same starting point, but I had a brain seizure and clicked out and back instead. I see partially what happened after reading this thread and others: the software took where I was and reversed it back thru the 75 percent of the loop to my starting point. But when I went to delete the newly generated starting point, my whole route was gone. Every point.
Suggestion: supplement your getting starting documentation to make it clear that out and back is for "when you want to follow EXACTLY THE SAME ROUTE in reverse back to the starting point".
And, I don't know if you can do this, but some kind of deletion warning like: "deleting this point will delete all the points on your route" would sure save people time.
I'd like to comment on this.
It would be useful to put some kind of indicator on the map stating that "out and back" has been used - this would make it clear to users.
If you make a mistake, and want to clear the out-and-back flag, the indicator would disappear, and the map should revert to being "point to point" or whatever the default is.
Mgm1001001's idea is also good. And this scenario is not a rare one, as jeff says.
In another post I point out that I need to create a "family" of routes that start at home, move to point B, and from point B (which is a long way from home and needs a lot of points to be accurate) fan out into at least 10 other out-and-back routes.
So please reconsider your decision to NOT allow undoing of "out and back" routes.
nick
I agree. I've run into this problem a number of times and have ended up resorting to just adding a training activity without a route because I didn't feel like going through the hassle of reentering everything again.
Great site though even with the bug.
Pete
I have run into this on the first three routes I ever entered and got really frustrated. I agree that undo should return the map to it's previous state - point in this case.
And I have an additional related issue. Today I created a point to point route - brand new route - clicked out and back and it doubled the route like I went out and back twice. I can't get it to not do that. I am resorting to creating everything point to point because it's faster and less frustrating at this point.
1 to 11 of 11