Why are multitouch axes intentionally not requested? #20
Comments
LinusCDE
added a commit
to LinusCDE/libremarkable
that referenced
this issue
Nov 4, 2020
canselcik
pushed a commit
to canselcik/libremarkable
that referenced
this issue
Nov 28, 2020
LinusCDE
changed the title
|
fixed by #21 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When trying to use the input_absinfo for ABS_MT_POSITION_X/Y, I noticed them being 0. After stracing the program, I noticed that most absolute axes on another device with abs axes were grabbed fine with an eviocgabs ioctl. But not my multitouch ones which evtest could clearly find.
My first finding that 0x28 was not all the ABS values (would be 0x3f) didn't work. The I noticed the comment below the finding which explicitly ignored the ABS_MT values.
It seems that I can grab the axis without problem. What was the intention of "we'll handle that later.". Is there any extra checking that needs to be done for those that I missed? For now my fix seems to work just fine (LinusCDE@43fb0b3). I needed the fix for this code to work.
The text was updated successfully, but these errors were encountered: