Automatic switch Distance to next Via Point / Final Destination

[Nick Carthew]

@Con-Hennekens No re- map, it’s default.

[Dae 0]

@Rajp said in Automatic switch Distance to next Via Point / Final Destination:

The “Automatic” option would then switch to displaying the duration and distance to the next via point and final destination on a timed basis, say every 3 to 4 seconds. That way you could see the summaries without having to manually select and switch. Of course, if there are no via points then just show the final destination summary

I made this same suggestion many months ago, as Scenic does this and it’s brilliant. It allows you to gauge the remainder of the day without having to mess about pressing buttons etc.

It’s especially handy if leading a group, as someone inevitably asks over the intercom what time lunch is or if we’re on time for the end of day arrival.

[Guzzist]

@Con-Hennekens said in Automatic switch Distance to next Via Point / Final Destination:

...This is no default method is it? Did you remap buttons?

Oh - how could be done a remap of remote controller buttons? I thought, only in settings, the correct remote controller must be selected.

[Jörgen]

@Guzzist the controller (like the BarButtons) is sending letters (as you can type on a keyboard). For Android there is an App (sorry, forgot the name) where you can remap what the controller sends.
This is helpful for controller that do not send the Keys you need for MRA.
I do not know what key is needed to switch the display.

@Nick, can you open an editor and push the button for the display change and let us know what letter is sent?

[Corjan Meijerink]

This is all listed in the manuals

Go to https://www.myrouteapp.com/support > "MyRoute-app" > "Bluetooth controllers".

For SilverFox, it's an "A"

[Con Hennekens]

As much as I understand some people's wish for this automatic switch, I just want to highlight also that it might draw eyes to the screen until your desired information comes along. It could be considered dangerous.

[Con Hennekens]

@Corjan-Meijerink, I get it... there is no A in BarButtons
(they could if they gave up repetitive zooming by long press).

[Rajp]

@Con-Hennekens alternate solution could be to tap that summary panel which then switches, tap again to switch back. So you can cycle through the various summary info by simply tapping that info summary panel.

[white.mouse]

@Rajp I think this is a better idea.
Having the constant change show is too distracting for my liking.
And going to the menu every time to switch is also inconvenient.
The solution is indeed what @Raip suggests. Just click on the screen in the box to switch.

[Jörgen]

@Con-Hennekens said in Automatic switch Distance to next Via Point / Final Destination:

@Corjan-Meijerink, I get it... there is no A in BarButtons
(they could if they gave up repetitive zooming by long press).

Too bad. Do you know someone who can extend the BarButtons code?

I will ask a friend, but is not easy.

[Con Hennekens]

@Rajp said in Automatic switch Distance to next Via Point / Final Destination:

@Con-Hennekens alternate solution could be to tap that summary panel which then switches, tap again to switch back. So you can cycle through the various summary info by simply tapping that info summary panel.

That's already the case long time...

[Con Hennekens]

@Jörgen, yes, Joost, the developer of BarButtons... But he has been very quiet for a long time already.

[Rajp]

@Con-Hennekens on the phone app yes, but not on CarPlay, sorry I was referring to CarPlay screen

[Jörgen]

@Corjan-Meijerink said in Automatic switch Distance to next Via Point / Final Destination:

This is all listed in the manuals

Go to https://www.myrouteapp.com/support > "MyRoute-app" > "Bluetooth controllers".

For SilverFox, it's an "A"

Hello Corjan,

I tried this out and compared it with the information on the support page. I first realised that all letters have to be sent as a code in lower case and not in upper case as described. (for BarButtons N=n, D=d and C=c)
I can not check this for Silverfox, but I think it should also be written in lower case here.

Assuming Joost (or someone else) changes the code and you could send an ‘a’ for the display switch, would you then add this function for BarButtons in MRA?