Mit dem Letzten Update wurde die Funktion „Wegpunkt überspringen" im Untermenü mit den … (3 Punkten) „versteckt".
Das ist am Motorrad etwas mühsam und unsicher trotz Bedienung über das WonderWheel auf der GS auf einem Carpuride W702BS und dauert einfach zu lange. Ich wünsche mir sehnlich, dass der Skip-Button wieder auf die Kartenansicht am linken oberen Bildschirmrand zurückkehrt.
Vielen Dank
Hallo @Markus_S,
Da meinst du vermutlich Kurviger in CarPlay. Wir haben ja mehr als eine Funktion in der Kurviger Navigation und diese daher gemeinsam in ein Menü gepackt.
Ich nehm dein Feedback aber mal mit, vielleicht geht es anderen auch so.
Wie oft kommt das denn real vor? Ich denke selten und wenn ist es einfacher und sicherer kurz anzuhalten und direkt auf dem AA/CP-Display die Funktion ausführen.
Ich mag das Clean-Design von Kurviger.
Ja, natürlich geht es primär um CarPlay auf meinem Navi-Nachfolger Carpuride.
Dieses Display spiegelt in erster Linie den Inhakt des iPhones (Kurviger) zur Navigation am Motorrad.
Skip Next Waypoint oder auch Skip Next Shapingpoint ist dabei eine wesentliche Funktionalität
die direkt über die Kartenansicht erreichbar sein sollte und nicht in einem Untermenü „versteckt" werden sollte.
Hallo @Kira!
Gibt es hier zwischenzeitlich vielleicht schon ein positives Feedback.
Ich war Mitte Juni 8 Tage in Frankreich und dabei habe ich den “Skip Waypoint” Button auf der Kartenansicht schmerzlich vermisst.
Ich würde mich freuen, wenn er bald wieder zurückkehrt, wo er war.
Vielen Dank und LG Markus
Hi @Markus_S,
Aktuell ist dahingehend nichts geplant. Wir beobachten das Thema aber weiter.
Somehow this topic has unfortunately fizzled out and there is still no return of the skip button to the main screen. That would be an improvement and a return to something better. Please give more likes and vote for it so that the “Skip Waypoint” button returns to where it belongs 
.
I suspect the developers consider the matter closed.
I would also like the SKIP button right on the screen, but apparently we’re in the minority.
Probably none of them are motorcyclists 
Actually, they are. Almost exclusively.
It’s just that probably few of them use a remote, WW, or a built-in controller with AA/CP on a daily basis.
I’ve been riding my motorcycle with AA/CP on a BMW with a multi-controller (WW) most of the time for over a year now.
So far, there has been very little feedback that it’s bothersome in the submenu. The UI actually has the advantage that you can see exactly what happens when you skip.
I don’t really understand the problem either. Yes, using AA/CP with the multi-controller (WW) in general is a pain. But how often do you really skip? I mean, on average I skip less than once per trip. However, with the multi-controller (WW), it has happened to me 3 or 4 times that I skipped by accident because I accidentally pressed the button by moving the multi-controller (WW) to the right — that was really annoying, having to stop, take off gloves, take the phone out of my pocket, and undo the change.
We are always open to feedback. So if it bothers more people, let’s definitely discuss it.
I found the original solution on the main screen to be much faster and more useful. Most people don’t even realize that the feature was ever on the main screen, let alone that it’s now in a submenu. So it makes little sense to argue with people who don’t know what they’re missing. It’s a mystery to me why something like that gets moved to a submenu. I don’t understand the argument about a „cleaner“ interface. On a 7" Carpuride, one extra round skip icon really doesn’t make a difference.
I definitely think it matters. Every button on the main screen takes up space, but not every user needs every button. Skip comes up extremely rarely for me and is an exceptional situation, so I don’t need it on the main screen (and don’t want it there either). Up to now, (+) and (-) buttons can also be found there, which you don’t really need because zooming via gestures is much easier.
Every button takes up map space and needs to be placed accurately. One misclick and you might have to stop and restore the previous state?
You could consider making button visibility configurable, but that also requires users to engage with the app.
However, settings are largely avoided as well; many expect a perfect config “out of the box”, which is impossible given the variety of desires.
With just a little practice, a skip is also triggered very quickly via (…) 
Had to learn recently that a remote control for Kurviger doesn’t help in combination with AA/CP.
Did you keep count of how many clicks it takes to delete 3 waypoints while driving? Every single time you have to go into the exact same submenu for each point. That’s many times more than deleting items three times in a row on the home screen. On top of that, I don’t want to have to pull over for this, because keeping my eyes on the road definitely suffers way more as a result. As for accidental deletions back when the skip button wasn’t there, I have to say that’s a user error if that „happens“ to you while driving.
(…), “Skip waypoint”, “Next”, “Next”, Skip. That’s 5. Or number of VPs + 2.
( assuming no shaping points, those are skipped implicitly )
However, it’s also unusual planning when VPs are set so close together and then have to be skipped in that quantity. For me, the VPs are spaced far enough apart that it practically never happens that I have to skip more than one.
An exception is aborting a tour with the goal of navigating directly to the destination.
In addition, “next” can also be operated as a “long” press.
What is your reason for setting the VPs so close together (and actually wanting to head to them), only to then skip them in groups?
For example, a roadblock before a mountain pass, another unforeseen construction site, or if part of a group wants to head straight to the hotel as a shortcut, or quite simply if someone else has planned something „daft“ and I want to take a different route. There are various reasons. But that’s not what this is about; it’s about the principle of functionality—that something which used to work is now „hidden“ in a submenu.
It may also happen that Bike Buddies don’t know the difference between WP and SP and share such routes with others. This often happens when recorded tracks are converted into routes or imported from other programs from a time when there was no distinction between WP and SP. I deliberately plan with WP and SP, but certain daily stages are too long for some or they let themselves be intimidated by bad weather.
Hi Markus,
I’m afraid the next person will come along and desperately need a fuel stop or a detour around a road closure… Or, or… Right there on the navigation interface. I agree with you that there are situations where certain buttons on the interface make sense, but also that this is just difficult to implement. If I remember correctly, at the time the skip function was introduced, the features for road closures and gas stations didn’t exist yet.
5 times as often, that’s about right. Completely incomprehensible.
I cannot accept the implementation argument, seeing as it was already implemented better.