EventClient vs. /dev/uinput
#1
I'm about to add support for a new input device. It appears that the recommended approach is to implement a new EventClient instance. Another option would be to inject input events to /dev/uinput. What are the advantages of using an EventClient over /dev/uinput?
Reply
#2
Without knowing anything about /dev/uinput it definitely sounds very linux-only but XBMC also runs on non-linux platforms.
Always read the online manual (wiki), FAQ (wiki) and search the forum before posting.
Do not e-mail Team Kodi members directly asking for support. Read/follow the forum rules (wiki).
Please read the pages on troubleshooting (wiki) and bug reporting (wiki) before reporting issues.
Reply
#3
Using /dev/uinput sends input events to the entire system, using an evenclient is XBMC only.
The advantage of uinput is it works on everything on your system, but only on linux and only locally, an eventclient only works on XBMC, but it works on XBMC on all platforms and it works over a network.

I'd just implement both Smile
Reply

Logout Mark Read Team Forum Stats Members Help
EventClient vs. /dev/uinput0