Zoom + / zoom - from external keyboard not working anymore with release 5.0.1 ?
-
A few years ago I wrote an appli running on a controler ESP32 to simulate an external keyboard.
It run approximatively like the Wunderlinq (although I did it before Wunderling exist) but less sophisticated.
I connect a MCP2515 module to the CanBus of my 2015 R1200RT LC itself connected to an ESP32 controler itself connect via BlueTooth to my Android phone.
The ESP32 & MCP modules are located under the pilot seat.
The actions made with the WonderWheel was sent to the phone (zoom +, zoom -, up, down, left, right).
At this moment I was only using Osmand and the main function used while driving was zoom + & zoom -.
When I added MRA app, the keyboard orders were working well (keyboard 'Standard', 43d = zoom +, 45d = zoom -).Since this time big changes have been done even on MyRouteApp and for the ESP32 boards.
Today, for the MyRouteApp, the map does not react to the commands (keyboard 'Standard', 43d = zoom +, 45d = zoom -).
Keyboard 'Wunderlinq' selected : no more change on the map but if a list is displayed (after pressing the upper right button) I can see the selected item changing upwards / downwards with a little ESP32 app sending KEY_UP_ARROW (218d), KEY_DOWN_ARROW (218d) alternatively (no change with 43d & 45d).
Zoom + and zoom - are still running today with the Osmand app (Keyboard 'Wunderlinq' selected, KEY_UP_ARROW, KEY_DOWN_ARROW keys).
A try with a former release of MRA should help but I can't do it by myself.
Summary : what code to send to get a zoom +/- on the map ?Any idea ?
Drive safe -
Have a look here under Wonderlink:
https://myrouteapp.freshdesk.com/en/support/solutions/articles/12000100670-bluetooth-controllers#WunderLINQYou also need to set the input to wonderlink in the app.
I believe you need KEY_UP_ARROW , KEY_DOWN_ARROW
Cheers!
-
When I use KEY_UP_ARROW et KEY_DOWN_ARROW (with Wunderlinq keyboard external keyboard selected of course) selected item in a list move upwards and downwards. The link is OK with my ESP32, but keycode is not correctly interpreted when a map is displayed.
It looks like the previous issue I met with the map frozen on the screen.
Another Android 9 facetie ?
