@alan_g said in xev like tool to see key_press (...) events:
They'll be on github or gitlab (UBports are migrating projects from one to the other).
I suspect you are misunderstanding me: OSK is not the solution you asked for, but it is the only process that does anything even vaguely like what you want. So, if you figure out how it is able to do that, you might be able to use that knowledge to create something new to remap input.
No, I didn't misunderstood you. I wanted to look into OSK to see which key-events are arriving there and what is assembled of them to route it to the apps.
I suggest that writing a new terminal app (or enhancing the existing one) with the ability to remap input would be far simpler.
Focus on the terminal-app could be done only when the events are arriving in it on a low level. In addition would mean that any other app could not be see the key-events which are possible with a BT keyboard. In the past I expanded already the mapping for the terminal app with json files like:
{
"name" : "mutt Keys",
"short_name" : "mutt",
"buttons": [
{
"main_action" : {
"type": "key",
"text" : "ESC",
"key" : "Escape"
}
},
...
Maybe a first step would be add some logging in the terminal-app to understand what chars are arriving there from a BT keyboard (not only from the OSK).
