Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11666] Touchscreen with (Py)Qt5 should use tslib instead of evdev
Date: Thu, 07 Feb 2019 09:37:08 +0000	[thread overview]
Message-ID: <bug-11666-163-hQoigulprS@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11666-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=11666

Tibor Stolz <tistolz@outlook.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WORKSFORME

--- Comment #1 from Tibor Stolz <tistolz@outlook.de> ---
Hello,

I found <http://doc.qt.io/qt-5/embedded-linux.html#touch>, which mentions some
more settings to be done by means of environment variables:

~> QT_QPA_EVDEV_TOUCHSCREEN_PARAMETERS='inverty' ./qt5test.py

This works for me, I get proper touchscreen input. (Hardware: BeagleBoneBlack
with 4D Systems gen4-4DCAPE-43T LCD)


There are two options to enable tslib:

~> QT_QPA_FB_TSLIB=1 ./qt5test.py

This seems to completely disable touchscreen input.

~> QT_QPA_EGLFS_TSLIB=1 ./qt5test.py

This seems to have no effect, i.e. touchscreen input works but is still y-wise
inverted.

Since there is no need for tslib in my configuration, as y-wise inversion can
be done without it, I declare this bug as RESOLVED WORKSFORME.

Best regards,
Tibor Stolz

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      reply	other threads:[~2019-02-07  9:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 15:45 [Buildroot] [Bug 11666] New: Touchscreen with (Py)Qt5 should use tslib instead of evdev bugzilla at busybox.net
2019-02-07  9:37 ` bugzilla at busybox.net [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-11666-163-hQoigulprS@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox