rvaiya

This is an interesting idea, and one I've toyed with myself. The main problem is that the only pointer data that can be recorded from the input device is in...

> @rvaiya: May I ask you as well about the use case you had in mind? Mainly to facilitate testing, but I can see how it might also have other...

@tkna91 It looks like this was a bug in upstream. Can you try building again?

Do you mean when `layer_indicator` is set to 1? Leaving it unset should have no effect on the caps lock indicator (unless by 'capslock' you actually mean 'toggling the shift...

Can you try the latest commit?

To clarify, are you suggesting that it works if you completely remove `layout_indicator` from your config? Or simply that it doesn't work at all unless you set it to 1?

Can you post the output of keyd itself using the latest commit? Also set KEYD_DEBUG=2 (E.g `make && sudo KEYD_DEBUG=2 ./bin/keyd`)

Sorry, I should have mentioned touchpads are currently unsupported. Adding support for this is non-trivial since a lot of work needs to be done on the raw touch events to...

I probably should have added some kind of special prefix to distinguish mice to begin with. At this point it would be a breaking change, but it might be worth...

I've added some device type prefixes (`m:` and `k:`) to the latest commit. Let me know how you get along with them.