John

Yes, IMO it's definitely worth it. The display/rendering should never block IO/CPU operations (as it happens now if I understood correctly).

In my opnion, the proper way would be to be able to hook on all keyboards, not only on the first one. And with a udev rule (or systemd perhaps?)...

I can work on it at the weekend, just need a few pointers to start. Can you describe what needs to be done so I can jumpstart on it?

We should choose the most performant and least costly way. I think the right way is to have an different instance, or maybe a thread for each keyboard input. I...

Yes sometimes this is the behaviour as yo describe it,but other times it works well, so I'm not entirely sure how to reproduce this consistently. As you said, it probably...

> > > > ... `touchcursor` repeats at a rate of 30, whereas the rest of the keyboard has a rate of 60. > > Do you mean that the...

I built the code, and commented out the "rehook" call and tried it. But unfortunately, it still manages to stay on the front of the queue. Is there a way...

You are right, it's not clear what can be done about this. I am not very familiar with the win32 hooking system in order to debug this in depth. So,...

After a few hours of debugging I managed to find the cause and how to fix it: in dllmain.cpp line 192 ``` // Sleep(1) seems to be necessary for mapped...