@David-Bonner said in TEST 123!: A really good idea Con Hennekens! Thank you! But I have to be honest: it is not entirely my idea. I have seen this before in another App, can't remember which one, I tried many. Also iirc my Zumo speaks a test sentence if you switch to another voice. So switch and switch back does more or less the same.

@Evert-Kuiken I agree, the arrow is sometimes hard to see.

@Jörgen said in I gave the new Beta app another go today.: I prefer a color that is not used on the map to prevent misunderstandings. Her, any powerful color. Indeed so. That is why Garmin’s magenta colour shows up so well. It does not clash with any of the other colours on display. You can see how well the yellow of the recorded track in MyRoute stands out against the blue, too. That though might clash against some roads (D roads in France for example) depending on the layer chosen to navigate over.

@Corjan-Meijerink I have seen the video which also explains the skipping of waypoint AND reinstating them. This is a great contribution. My points have now become less relevent although it might be handy to skip some by my co-pilot during driving (without a stop) and extensive work.

@David-Bonner Thanks for the follow up!

@Corjan-Meijerink said in Current location ‘On / Off’: Details like this are probably improved before the release to make sure it’s clear for all! Even better

@Ronni Bigger text is something we will continuously look at. Currently we are pretty satisfied with the accessibility but increasing size even more causes quite some layout issues on smaller devices. We need to update our UI to be way more responsive to make this a scalable solution. This is something we aim to do before the release Streetnames cannot be hidden at this point but it has been suggested before to make this possible: https://forum.myrouteapp.com/topic/3125/hide-streetname-in-direction. At this point we still see is as quite a fundamental part of the navigation so therefore it cannot be hidden (yet). I guess this will be implemented as it is quite easy to do The upcoming waypoint can already be turned on / off in the settings!

Het is gewoon de standaard voor alle navigatie apps, waarom dat zo is, weet ik ook niet. Opzich levert het een goed contrast op maar uiteindelijk is dat voor iedereen weer anders.

@Corjan-Meijerink thx

@Evert-Kuiken dat is bewust zodat je de interactie met de achterliggende kaart behoudt Nogmaals op het kaartlagen icoontje klikken sluit trouwens ook.

@Corjan-Meijerink I think Con (his reply to my post) is right. It might well have to do with these locations having addresses that do not match in the right way with their physical location for navigating.

@Corjan-Meijerink Thanks for adding to the wishlist. I understand prioritizations

@Herko-ter-Horst Thanks for the ideas, we'll see what we can do about it in the future updates For now, keep giving us this excellent feedback! I really appreciate the time you take to share it with us.

Thanks for the vivid discussion here! Love reading the pro’s and con’s. To only partly comment: a combination between (hybrid version) of track navigation and waypoint information / features is very difficult if not impossible at this point. Especially given the resources spent in all other crucial features / community suggestions So for now: keep the conversation going and we’ll see where it all ends. I am happy to see people using track navigation and testing it properly.

@David-Bonner I agree with David's suggestion the distance and time displayed to a Via point - rest stop and then final destination. no need to announce each shaping point. Suggestion: I would like to see the font for the posted mileage be a little bit bigger and make the time of arrival display a little smaller..

@Corjan-Meijerink OK, no problem. I'll always arrive sooner than planned or I take the motor

@Tumbleweed It wasn’t supposed to be ready yet We aim to have a first Beta of CarPlay end of this month

@G-Grote-Ganseij Bedankt voor de positieve woorden!

@Gerard-23 Correct! Dat werkt even niet meer zoals het hoort, in de aankomende update (eind deze week) is dat weer opgelost!

@Gerard-23 Bedankt voor het delen. We hebben het inderdaad constateren en gelijk opgelost! In de volgende update zal het probleem dus definitief verholpen zijn.