New component for keyboards and panels.

To use the pin events you would not connect sendkeys keycode input
(as all inputs would be pins)

This way you can verify sendkeys operation standalone
(no 7I73 or matrix_kb required)

Ultimately I also suspect it would be more reliable to capture keycodes
with matrix_kb (since its real time) and use individual hal pins from
matrix_kb to sendkeys pin events

I don't really understand what he means.+

I have another question. From what I understand, the SENDKEYS component is created to send keys, that is, as if it were a virtual keyboard. And I understand that you can use the keypad inputs of the 7i73 as inputs to simulate these keys, I don't know if I'm wrong. Unfortunately I have searched in the for or some real example of the use of this component and I have not found it. In this same thread at the beginning andypugh shows a video of the use of this component but through another card. So from what I understand from that video this component would have to be used independently of the 7i73 using other different inputs.

What I mean is that you should be able to setup
sendkeys to send keystrokes by setting its input hal pins

This would allow you to verify sendkeys operation
without using any other components, In the example,
sendkeys.0.trigger-01 sends a space so if you

setp sendkeys.0.trigger-01 true

you should get a space pushed into the keyboard buffer

Thanks for your support, what I understand is that I can use the 7i73 as key input and convert these HAL pins to keystrokes.

Yes, but to determine why you are not getting keystrokes, it would be
valuable to see if sendkeys works by itself...

I tested the 48 keyboard matrix, it works fine.
I want to use numeric keys and some keypads of the screen gmoccapy.
From HAL, I tested, run a specific task. loadusr -W sendkeys config=16t2
setp sendkeys.0.trigger-01 true. and check in hal show it works
Could you please provide an example Hal's component procedure that works with a matrix keyboard?
Thank you.
 

Could you post your configuration?

"Yes, but to determine why you are not getting keystrokes, it would be
valuable to see if sendkeys works by itself.." Thanks for your support, but the truth is I don't know exactly how to do what you tell me, I think it refers to using commands like halrun, loading that component and so on.

If you take your test configuration and simply

setp sendkeys.0.trigger-01 true

a space keystroke should be created
(to do it again you would need to

setp sendkeys.0.trigger-01 false
setp sendkeys.0.trigger-01 true

The problem is that I followed the instructions given by andypugh in SENDKEYS to get permission to write to /dev/uinput and it wasn't working. I had to do it manually with sudo chmod 666 /dev/uinput. Since I'm using the rasperry PI4 every time I rebooted it, it again took away my permissions to write to uinput, I solved it by adding the command @sudo chmod 666/dev/uinput so that it runs automatically when the PI4 is rebooted. Now the problem is that according to andypugh's instructions, to see which event each key pressed corresponds to, the component must be loaded and and open a halmeter showing sendkeys.0.current-event. but this pin in halmeter always shows -1 even though if you write to the terminal the character corresponding to the key pressed.