sketch wrote:CBenson wrote:I'm not sure what "the error" is. Seem to mostly be a display problem with the routes shown in URs as discussed for example here and here. It may actually effect the user when the endpoint of the route is on one of the two segments that connects the same two junctions.
Your post, the second post, in the first thread you linked shows a user that followed the "display bug" route rather than the TTS route. I don't think it's reasonable to consider something as important as the route line being displayed incorrectly is so minor as to be considered merely a "display bug". Especially when the user isn't using sound. Is the user more likely to follow the arrow in the corner, or the route line on the screen?
Understood. But I've never actually been able to get confirmation from a user that they were actually following the route line in a conversation on a UR like this. I certainly can't say it doesn't happen, just that I haven't been able to verify it. On the other hand I can say that sometimes the purple route line in the UR is not the same as the purple line in the client, because that has happened to me. Notwithstanding, I think it is worthwhile to add the extra junctions at this point.