From: "Björn Kirchner" <bjoern@am-soft.de>
To: buildroot@busybox.net
Subject: [Buildroot] Fwd: Qt4 Application - Touch detection
Date: Thu, 15 Jan 2015 21:22:31 +0100 [thread overview]
Message-ID: <20150115212231.08000b68@tux.kirchner> (raw)
In-Reply-To: <CADKZYYL-uKCvyEU9w7eAWi-yZv4bky5dTEz+RpUNAJQchjw2-Q@mail.gmail.com>
Am Thu, 15 Jan 2015 14:01:14 -0600
schrieb Santhosh Ramani <srcoolz@gmail.com>:
> Hello Bjorn,
>
> Thanks once again for your reply.
>
> Does the capital 'T' in "Tslib" make any difference? I've only seen
> > it written as 't', yet. Do you reboot between calibration and
> > starting of your program? In my case the devices changed
> > occasionally between reboots, so /dev/input/event0 was not always
> > the correct device.
>
>
> I tried with both options, but the results are the same. In my case,
> it's always /dev/input/event0 so I think I'm okay here.
>
> I'm not quite sure here. If you start a script which exports
> environment
> > variables, I think those exportes variables only exist in this
> > script and in its child processes. So, if you start ts_calibrate
> > with a start script and after that your program from a differnt
> > script or directly from your login shell, I suppose those variables
> > aren't set anymore. Please try to export them either in a start
> > script for your application or, as a quick test, in the shell you
> > use to start your program. Just to make sure...
>
>
> I tried exporting the variables from command line along with the
> scripts and also the method you suggested, but there was no change in
> operation. I was able to run the qt examples and once I exported the
> variables from command line those examples worked fine.
So, you did something like this?
# export TSLIB_TSDEVICE=/dev/input/event0
# export QWS_MOUSE_PROTO="tslib:/dev/input/event0"
# <qtExample>
And there the touch screen worked correctly? And your program didn't?
>
> I'm going to try to compile my Qt application with the library built
> by buildroot and see if that helps. Do you have any other suggestions?
>
> Thanks
>
> - Santhosh
next prev parent reply other threads:[~2015-01-15 20:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 17:03 [Buildroot] Qt4 Application - Touch detection Santhosh Ramani
2015-01-15 17:13 ` Björn Kirchner
[not found] ` <CADKZYYKDoizsdEo28Ynwb=ndhJXmHW3Zoqx=aSpP-1BMnDYujw@mail.gmail.com>
2015-01-15 17:57 ` [Buildroot] Fwd: " Santhosh Ramani
2015-01-15 19:06 ` Björn Kirchner
2015-01-15 20:01 ` Santhosh Ramani
2015-01-15 20:22 ` Björn Kirchner [this message]
2015-01-15 20:44 ` Santhosh Ramani
2015-01-15 21:04 ` Charles Krinke
2015-01-15 22:09 ` Santhosh Ramani
2015-01-15 22:27 ` Charles Krinke
2015-01-15 23:33 ` Santhosh Ramani
2015-01-16 5:53 ` bjoern at am-soft.de
2015-01-16 17:26 ` Santhosh Ramani
2015-01-16 18:10 ` Charles Krinke
2015-02-01 1:33 ` Santhosh Ramani
2015-01-16 5:49 ` bjoern at am-soft.de
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=20150115212231.08000b68@tux.kirchner \
--to=bjoern@am-soft.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.