View Single Post
Old 01-21-2021, 12:12 PM   #202
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
@Acorn: Yeah, the current approach is to kill all the things and restart Nickel on exit (c.f., KOReader).

And, no, unfortunately, libinput is not usable on the Kobo, for... reasons. (Mainly, it requires an up to date kernel & userland (mainly, udev), which, much to my dismay, is... *really* not a thing on Kobo ;p).

libevdev does work, on the other hand, but it's much lower level than libinput. (I use it in KoboUSBMS, although not for touch input, because touch input is hell on Kobo. And, also, I don't need it ^^).
[Given the mess you'll have to parse and make sense of, it's not necessarily a bad thing, though].

tslib, a much older project, can also be coerced into behaving, but it's slightly old-school, and is potentially less amenable (without dirty, dirty hackery at the C level) to the kind of trickery needed to translate the mess that is generated by the various Kobo input devices to something it understands than libinput might have been .

Last edited by NiLuJe; 01-21-2021 at 12:20 PM.
NiLuJe is offline   Reply With Quote