01-16-2024, 03:53 PM
Looking back at the Guide I created three years ago, Using FLIRC and other input devices for remote control, I see that i used a wildcard to scan all the input events. Specifically, to see and save the keyscan codes as I pressed keys, I did
I'm curious to know if this works for your case as well, rather than having to laboriously dig through the Linux arcana. Seems to me it should as long as you press only keys and don't move the mouse.
It seems the older I get, the more quickly I forget the stuff I have done before. Used to take me over decade to forget; now it takes about 18 months. The trend isn't reassuring.
Regards,
Kent
Code:
thd --dump /dev/input/event* | tee keycodes.capI'm curious to know if this works for your case as well, rather than having to laboriously dig through the Linux arcana. Seems to me it should as long as you press only keys and don't move the mouse.
It seems the older I get, the more quickly I forget the stuff I have done before. Used to take me over decade to forget; now it takes about 18 months. The trend isn't reassuring.
Regards,
Kent
