- Posts: 18115
- Thank you received: 5334
New component for keyboards and panels.
- PCW
- Offline
- Moderator
-
Less
More
3 years 2 months ago #277494
by PCW
Replied by PCW on topic New component for keyboards and panels.
Yes, but to determine why you are not getting keystrokes, it would be
valuable to see if sendkeys works by itself...
valuable to see if sendkeys works by itself...
The following user(s) said Thank You: COFHAL
Please Log in or Create an account to join the conversation.
- SOLD
- Offline
- Premium Member
-
Less
More
- Posts: 122
- Thank you received: 13
3 years 2 months ago #277542
by SOLD
Replied by SOLD on topic New component for keyboards and panels.
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.
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.
Please Log in or Create an account to join the conversation.
- COFHAL
- Offline
- Platinum Member
-
Less
More
- Posts: 461
- Thank you received: 62
3 years 2 months ago #277543
by COFHAL
Replied by COFHAL on topic New component for keyboards and panels.
Could you post your configuration?
Please Log in or Create an account to join the conversation.
- COFHAL
- Offline
- Platinum Member
-
Less
More
- Posts: 461
- Thank you received: 62
3 years 2 months ago #277580
by COFHAL
Replied by COFHAL on topic New component for keyboards and panels.
"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.
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.
Please Log in or Create an account to join the conversation.
- PCW
- Offline
- Moderator
-
Less
More
- Posts: 18115
- Thank you received: 5334
3 years 2 months ago #277586
by PCW
Replied by PCW on topic New component for keyboards and panels.
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
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
Please Log in or Create an account to join the conversation.
- COFHAL
- Offline
- Platinum Member
-
Less
More
- Posts: 461
- Thank you received: 62
3 years 2 months ago #277745
by COFHAL
Replied by COFHAL on topic Solved
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.
Please Log in or Create an account to join the conversation.
Time to create page: 0.443 seconds