-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No touch input on Libra 2 #3
Comments
Weird, should be working Hmm |
When launched that way, I get the following output:
The window appears on the device as expected, still not frozen (clock updates still happen), but this time if I touch the screen the window disappears and I'm back to seeing (and interacting with) Koreader instead. In this state, I'm still getting a partial update from Sanki near the top of the screen when the time changes: but all touch events go to Koreader, and nothing new is output in the terminal where the command is running (except for a few more |
Turn off koreader, kill it from the terminal from htop, then launch sanki and touch the screen a few times for logs Koreader is grabbing the input device for himself :-( |
That seems to put me into a similar state as when I launch Sanki from NickelMenu (i.e. Sanki is visible, but touches anywhere on the screen do nothing) |
Well, any logs then? |
After adding
But still no further output when touching. With the addition of Here's some samples: Touching near the top-left:
Near top-right:
Near lower-left:
Near lower-right:
|
Interesting. Try some arguments with rotation and swapping the axes. As you can see they are unconfigured in some way resulting in some madness. Im top right you should get max x and 0 y values in pixels ( it goes (x, y)). In bottom left (0, max y) and bottom right ( max x, max y) |
This project looks pretty cool! I just tried to run the latest Nickel release on my Kobo Libra 2, and though the main window appears and looks normal, the app doesn't respond to touch inputs. The clock still updates, so I don't think it's a crash/hang.
The text was updated successfully, but these errors were encountered: