Thread: Being the only one capturing touch input?
View Single Post
Old 01-31-2023, 04:14 PM   #2
katadelos
rm -rf /
katadelos ought to be getting tired of karma fortunes by now.katadelos ought to be getting tired of karma fortunes by now.katadelos ought to be getting tired of karma fortunes by now.katadelos ought to be getting tired of karma fortunes by now.katadelos ought to be getting tired of karma fortunes by now.katadelos ought to be getting tired of karma fortunes by now.katadelos ought to be getting tired of karma fortunes by now.katadelos ought to be getting tired of karma fortunes by now.katadelos ought to be getting tired of karma fortunes by now.katadelos ought to be getting tired of karma fortunes by now.katadelos ought to be getting tired of karma fortunes by now.
 
Posts: 219
Karma: 3333683
Join Date: Nov 2019
Location: United Kingdom
Device: K5, KT, KT2, KT3, KT4, KV, PW2, PW3, PW4, PW5
Quote:
Originally Posted by lsmeni View Post
Hi all!

By following the amazing research done by this community , I've managed to capture touch input by reading on /dev/input/event1. However, the touch events still got forwarded to the current displayed applet. Because I'm planing to use these events for a fullscreen application (drawn by fbink), that behavior would be undesirable...

Is there a simple workaround to be the only input reader?
You want the EVIOCGRAB ioctl, here's an example of using it to capture input devices in C.
katadelos is offline   Reply With Quote