MobileRead Forums - View Single Post

kiwilex · 09-09-2020, 11:37 AM

Thanks nuetron for your proposition.

I had few time and some issue to update qt runtime libs until I get traces for the evdev touch ouput, so my progress is slow.

It appears that the coordinate is correct (the orientation should be flipped from the one shipped in the initial launch script). But no contact point is generated by Qt when the EV_SYN signal is received since nothing happens and there is no trace message generated.

My guess after looking at Koreader touch handling is that there is a special management to have for the EV_SYN that is called snow protocol for the H2O2. It seems that the without it the touch message is not standard. I need some time to figure out what is behind the comment "reset every slot that doesn't appear in the current touch event (because on the H2O2, this is the only way we detect finger-up)".

Perhaps someone passing by might help and give some explanations :-).

09-09-2020, 11:37 AM	#40
kiwilex Member Posts: 14 Karma: 10 Join Date: Sep 2020 Device: kobo	Thanks nuetron for your proposition. I had few time and some issue to update qt runtime libs until I get traces for the evdev touch ouput, so my progress is slow. It appears that the coordinate is correct (the orientation should be flipped from the one shipped in the initial launch script). But no contact point is generated by Qt when the EV_SYN signal is received since nothing happens and there is no trace message generated. My guess after looking at Koreader touch handling is that there is a special management to have for the EV_SYN that is called snow protocol for the H2O2. It seems that the without it the touch message is not standard. I need some time to figure out what is behind the comment "reset every slot that doesn't appear in the current touch event (because on the H2O2, this is the only way we detect finger-up)". Perhaps someone passing by might help and give some explanations :-). Last edited by kiwilex; 09-09-2020 at 11:39 AM.