‘N’ problem - is it my keyboard?

[Michael Wilkinson]

I have noticed recently that when using the Route Lab on my 10th generation IPad with Logitech keyboard pressing the ‘n’ causes the app to return to the Route planning home page.

This is evident whenever the key is pressed. Any route being worked on at the time is saved and can be returned to via the ‘recent routes’ button

This does not occur when using the same app on my IPhone, and there does not appear to be any issues with the keyboard or the ‘n’ key in other apps or searches

Any suggestions? Could it be a fault on the keyboard (it’s new and I guess I can return it); or is it a glitch in MRA?

UPDATE - after further investigation I noticed that the issue does not occur when using the on screen keyboard. I have concluded that my accessory keyboard is at fault

[Herko ter Horst]

@Michael-Wilkinson I would recommend waiting for a response from someone with knowledge about the way Bluetooth keyboards (and devices that act like them, like bar buttons) are handled within the app, before returning your keyboard, because I think I've seen similar comments before.

[Con Hennekens]

@Michael-Wilkinson, Like Herko said, it has been mentioned before indeed. This is probably due to the special function the N key has for hardware controllers. You will probably find more keys with special functions. While navigating, pressing the N key has a kind of "back" function. By using Routelab through the App itself, the app keeps activating these functions which are intended for navigating, not for using routelab.

If you start Routelab in your browser instead of via the app, it will work as intended. The routelab button in the app is nothing more than an embeded webpage view afterall.

@Corjan-Meijerink, can these controller key traps possibly be limited to to navigational functions, or excluded from the embedded browser?

[Jörgen]

Hi,

"n" is used in the navigation app to open the menu. I am not sure if there is a correlation?

[Michael Wilkinson]

@Con-Hennekens Thank you for your comments and advice. You’re correct - if I open via Safari there isn’t a problem

[Con Hennekens]

@Jörgen, I just simulated this with the BarButtons, so I am quite sure there is a correlation now

[Corjan Meijerink]

Fixed in the 4.1.0 release