David
David
This one is quite unlikely as it would require to refactor how key presses work. Maybe someone else can expand on this. The TL:DR is too much effort for a...
Have you made any progress here @mergen3107, i am now slightly interested in having it…. 😅
no worries @mergen3107... ``` 02/24/25-17:06:17 DEBUG key event => code: 108 (Down), value: 1, time: 1740413177.167955 ... 02/24/25-17:06:17 DEBUG key event => code: 108 (Down), value: 2, time: 1740413177.529910 02/24/25-17:06:17...
it works!!!! these lines here say that we only care about key_repeats from page turn buttons BUT, on kindle page turn buttons don't have key repeat events (according to mergen's...
well I am glad I didn't jump to assumptions then. Well it turns out that a simple `or keycode == "Up" or keycode == "Down" or keycode =="Left" or keycode...
honestly it works impressively well out of the box. Would this be an acceptable PR? `or keycode == "Up" or keycode == "Down" or keycode =="Left" or keycode == "Right"...
> (Btw, the comment says it was written with a Kobo Forma in mind.) it is that and the fact that I didn't need to add anything to device.lua that...
well I've come up with something like this, but I already can see @NiLuJe waving furiously at the back. ```diff diff --git a/frontend/device/input.lua b/frontend/device/input.lua index 3fbbfa80352a..6dec84a3ebb3 100644 --- a/frontend/device/input.lua +++...
> I'm kind of curious about the "linux phone", whatever that is :D at least I wasn't the only one scratching my head wondering what that is. Must be some...