View Single Post
Old 07-21-2024, 03:34 AM   #287
sublipri
Enthusiast
sublipri can self-interpret dreams as they happen.sublipri can self-interpret dreams as they happen.sublipri can self-interpret dreams as they happen.sublipri can self-interpret dreams as they happen.sublipri can self-interpret dreams as they happen.sublipri can self-interpret dreams as they happen.sublipri can self-interpret dreams as they happen.sublipri can self-interpret dreams as they happen.sublipri can self-interpret dreams as they happen.sublipri can self-interpret dreams as they happen.sublipri can self-interpret dreams as they happen.
 
Posts: 32
Karma: 20342
Join Date: Jul 2023
Device: Kobo Glo, Kobo Sage
Quote:
Originally Posted by NiLuJe View Post
We talked briefly on Discord a while ago, did we?
I don't think we've ever talked before - I don't use Discord.

Quote:
I implemented fbink_input_scan a few weeks ago, that should help with input device discovery .
fbink_input_scan looks useful! I'll try out using that in the future.

Quote:
* About that comment, does it behave in ftrace itself?

And if it doesn't, can you post the full results from a devcap test? (`make devcap` in FBInk, everything to run will end up in the generated tarball).

Also, *how* was the device forced into landscape?
I tried running finger_trace on the Glo and it doesn't behave properly in landscape (but does in portrait). Swiping from the bottom left to the top left (relative to landscape) leads to a line being drawn from the top right to the bottom right.

I'm forcing the Glo into landscape by setting ForceAllowLandscape=true in Kobo eReader.conf and then selecting Landscape rotation in Nickel. I've attached the results of a devcap test.

Quote:
Originally Posted by NiLuJe View Post
Oh, perhaps more importantly: you might want to swap axes *before* mirroring, otherwise you end up mirroring the wrong axis .
I had originally swapped the axes before mirroring like in ftrace, but that didn't work. I tried a whole bunch of things without really understanding what I was doing (I'm terrible at maths ), and the current code was the only way I could get it to work on my devices. I thought perhaps since I'm translating the coordinates from canonical to native rather than native to canonical, that swapping the axes at the end was the correct thing to do. But I don't really understand why it works or whether it will actually work on other devices.
Attached Files
File Type: gz Kobo-DevCap-Results.tar.gz (9.5 KB, 223 views)
sublipri is offline   Reply With Quote