I figured out my issue.

I set the following environment variable:

QT_QPA_EGLFS_DISABLE_INPUT=1

Of course, the cursor dissapears, but when pressing around my Gui running on the Compositor I'm not noticing any buttons being pressed except when I press in them, so that's definitely preferred to a wonky cursor!

May I suggest to change for Python 3 ?
Python 2.7 will reached end of life next year so it's not a good idea to start a new project with it.

Hi,

Well, evdevtouch plugin seem to be completely buggy.
The rotation woks very well but afin 1 to 10 secondes, the touch does not woks anymore.
Even with example programs.

I have this information :
TouchPointPressed without previous release event QQuickEventPoint(accepted:false state:Pressed scenePos:QPointF(249.631,798.957) id:2000002 timeHeld:0)

I have to reset the application to work.

Is there any solution to workaround this bug or a solution with libinput ?

Thanks again for your input @tekojo. I'm not 100% sure on the gloves just yet, likely a mixture of synthetic, leather and suede. I'll keep the sliders for now, and will give them a thorough test once my hardware is setup.

Thanks for your help.

It's an application that runs on a big screen that people will use standing up. So they will be using touch rather than a keyboard.

The reason for Windows 7 is that the application will need to attach to hardware, D2K-DASK http://www.adlinktech.com/PD/web/PD_detail.php?pid=350. The hardware drivers are only guaranteed for Windows 7 and 8. Its possible it might work on Windows 10 anyway but it's not clear.

Also, they want to use a touch number pad for number only entry. Not sure how much extra effort that would involve? I just found this artical http://www.cplusplus.com/forum/windows/128603/ , is ok?

@chaithubk
Are you reading from your device

continously
or just reading from it when device notifies you that data has arrived

In the scenario 1 device will misbehave like you have mentioned

For your screen mouse area, have you tried this?

MouseArea { anchors.fill: parent onPressed: { // your stuff here, e.g. global timeout reset mouse.accepted = false; } }

@etiennedm Why don't you just use layouts?

@Silveyra Probably, libqtslibplugin.so file under directory qt/plugins/generic/
Please correct me if I'm wrong.

Hi,

You have several wiki pages about Qt and the Raspberry Pi, see here for a start.

Driver was the the right way to go, thanks for pointing this out.

It turns out that the driver had a calibration method built in, but the transform matrix was not set to change the coordinates. I calculated the new matrix values based on the max coordinates displayed by evtest and the actual coordinates of the framebuffer, plugged them in to the driver code, compiled and ... it works!. Evtest displays correct coordinates and Qt works correctly with no tslib.
I don't like the fact that calibration matrix is hardcoded into the driver, but I consider fixing this an extracredit activity to be done sometime in the future.

@dzimiwine I tested 5.5.0 beta and it works fine

I'll try that.
Thanks

add -tslib and recompile qt and chart example but not solved ! ./configure -prefix /opt/installed/arm/QtEmbededd-5.4-static-tiny210/ -opensource -confirm-license -no-xcb -xplatform linux-arm-gnueabi-g++ -nomake examples -feature-THREAD -feature-CONCURRENT -feature-SOUND -feature-EFFECTS -no-openssl -lpthread -optimized-qmake -no-cups -qt-zlib -static -qt-libjpeg -qt-libpng -qt-sql-sqlite -qpa linuxfb -linuxfb -tslib

export TSLIB_FBDEVICE='/dev/fb0'
export TSLIB_TSDEVICE=/dev/touchscreen-1wire
export TSLIB_PLUGINDIR='/usr/lib/ts'
export TSLIB_CONFFILE='/etc/ts.conf'
export TSLIB_CALIBFILE='/etc/pointercal'
export TSLIB_CONSOLEDEVICE='none'
export TSLIB_TSEVENTTYPE='INPUT'

export QT_DEBUG_PLUGINS=1 cat /dev/touchscreen-1wire | hexdump
0000000 0fff 0fff 07c6 8629 07c5 8626 07c5 8626
0000010 0fff 0fff 0966 85bb 096c 85b9 0968 85a8
0000020 0968 85a8 0fff 0fff 0964 85ba 0938 85a9
0000030 08ba 8571 085d 8559 07a1 8573 0736 8599

$chartthemes -platform linuxfb -plugin tslib
QIconvCodec::convertToUnicode: using Latin-1 for conversion, iconv_open failed
QIconvCodec::convertFromUnicode: using Latin-1 for conversion, iconv_open failed
QFactoryLoader::QFactoryLoader() ignoring "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.2" since plugins are disabled in static buils
QFactoryLoader::QFactoryLoader() ignoring "org.qt-project.Qt.QPlatformInputContextFactoryInterface" since plugins are disabled in static builds
QFactoryLoader::QFactoryLoader() ignoring "org.qt-project.Qt.QGenericPluginFactoryInterface" since plugins are disabled in static builds
QFactoryLoader::QFactoryLoader() ignoring "org.qt-project.Qt.QStyleFactoryInterface" since plugins are disabled in static builds

@phil999
I too have struggled with getting the Tslib touchscreen implementation to work. I've spent a lot of time sprinkling print statements around in the Qt code figuring out what is going on. What I've learned is this:

Tslib and Evdev are separate implementations that are NOT equivalent. The Tslib implementation was developed for single touch (generally resistive) touchscreens while the Evdev implementation was developed for multi-touch (generally capacitive) touchscreens. For single touch screens, every action possible can be characterized as an equivalent mouse operation and that is what Tslib does. (Note that the Tslib plugin calls handleMouseEvent, not handleTouchEvent). Conversely the Evdev implementation does handle multi-touch which has no mouse equivalent so Evdev characterizes the touchscreen events as touch events.

You MUST get your touchscreen properly calibrated so that the coordinates are within the screen dimensions. Mouse events will only be reported to an object if they are within the object. Try recalibrating the touchscreen (ts_calibrate) and then run ts_test to be sure the touchscreen operation is correct. (We found that some versions of ts_calibrate don't work correctly and made some changes in the code ourselves.)

Event type 50 is a notifier event that I believe is triggering the QTsLibMouseHandler::readMouseData(). You can ignore these.

Your event filter should be looking for Mouse events. Probably these will be GraphicsSceneMousePress, GraphicsSceneMouseRelease, GraphicsSceneMouseMove, GrabMouse and UngrabMouse. (But this is object dependent.) I was using the qtbase/examples/touch/knobs application for test and debug and in the Knob::sceneEvent() function in knob.cpp, I changed the case statement to look for those 5 events. On a touch-drag-release I typically see the following sequence:

GrabMouse
GraphicsSceneMousePress

A variable number of GraphicsSceneMouseMove

GraphicsSceneMouseRelease
UngrabMouse

Be sure to intercept these events and not call the default QGraphicsItem::sceneEvent() handler. It will inhibit seeing all of the above events except the initial GrabMouse and GraphicsSceneMousePress

Hope this helps!