Qt5 Raspbian eGalax Failing touchscreen interaction

migsada

Thank you learc83, with evdevmouse works.

koalo

Is there any possibility to calibrate evdevmouse?

Tannyveer

Hi
I am working on touch based Qt appliction in raspberry pi.
after running my Qt app touch screen cannot respond. It shows error on qt app terminal like "evdevtouch: Could not read from input device (No such device) "
i will try the plugin s
-plugin evdevmouse:dev/input/event1
-plugin tslib:dev/input/event1 cannt work for me

but when i used the -plugin evdevtouch:dev/input/event1 it shows
evdevtouch: Invalid ABS limits behaviour unspecified

please give me any suggestions

learc83

Your touchscreen is definitely event1? Is your touchscreen multitouch? Does it work outside of Qt?

Tannyveer

My touch screen is egalax 7 inch touch screen i check the touch scrren event i.e is 1 only

learc83

Is it working outside of Qt, that is can you use it in Raspbian or whatever OS you're using?

Looking through the Qt source code the warning you're getting is caused when the touchscreen doesn't respond correctly to a system call asking for the minimum and maximum of the x y values.

If that is the case then I'm not really sure what you can do about it.

There was, however, a fairly recent patch to this system call in the source code. Are you running the latest version of Qt5?

learc83

I also found another person using your touchscreen who got it to work with tslib instead of evdevtouch.

http://qt-project.org/forums/viewthread/24199

Tannyveer

Yep i am using raspbian os and Qt5.
Is it posible to rut Qt5 apps with this egalax touchscreen.
If it is working please guide me, i was struck from last 5 days.

learc83

I haven't used a egalax touchscreen so I don't know. However the person on the thread I posted above seemed to be able to get one working With Qt5 using tslib.

Sebastian82

PING
I uses actually an eGalax 7" Touchscreen. Touch input inside of the QT Application is done by TSLIB, but an interaction with the desktop in the background is still there ... why ??? is there a way to fix this ?

Regards

Sebastian