View Single Post
Old 07-22-2019, 11:11 AM   #5
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
You'll always need *something* the poll the input device . However you implement that is up to you, though. If you're okay with reacting to the barest random brushes, you can simply poll it and react to the first thing that comes up (random Google link that is completely random and I haven't actually read: https://www.linuxjournal.com/article/6429). Just keep in mind that "one touch == *multiple* evdev events" with a touchscreen, it's less straightforward than a keyboard where you basically only get keydown/keyup/keyrep & sync events.

But if you need to react to only some *specific* things, you'll either have to decode it yourself (it's actually fairly straightforward, we've had people doing it in shell over in Kobo-land), or rely on something that does it for you (f.g., evtest).

Last edited by NiLuJe; 07-22-2019 at 11:17 AM.
NiLuJe is offline   Reply With Quote