From: Martin Jansa <martin.jansa@gmail.com>
To: Marco Cavallini <m.cavallini@koansoftware.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: xinput-calibrator
Date: Thu, 4 Feb 2010 12:31:45 +0100 [thread overview]
Message-ID: <20100204113145.GR3401@jama> (raw)
Hi,
I've seen your patches for xinput-calibrator. I'm not sure if you're
the author (github is down now ;/), but maybe you could add this
anyways.
For shr I've added small shell script to run calibration only if
/etc/pointercal.xinput doesn't exist and after calibration store values
there for next reboot.
http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=48dd2427c14edb8349e9f16150ad0f9c037c2ab8
This is then used in Xsession.d script.
Problem is when user wait too long when starting xorg for first time and LCD
screen is blanked, then first touchscreen tap to unblank it counts as
first point for calibration (way off the right mark).
I've workarrounded it with forcing LCD to stay on while calibrator is
running but still not best solution (ie user can touch ts by accident
even with display on.
Could you add option (ie enabled by command line param, or even by
default) to repeat calibration when user doesn't confirm that he did it
right and touchscreen is working for him?
Something like (while still in xinput-calibrator gui):
Do you want to use/store calibration values?
If yes, press touchscreen for 10s.
If no, press once and calibration will start again.
(maybe some 3rd option to exit calibration without storing)
(buttons would be easier to use, but difficult to press the right one if
user messed calibration really badly).
Thanks!
--
uin:136542059 jid:Martin.Jansa@gmail.com
Jansa Martin sip:jamasip@voip.wengo.fr
JaMa
next reply other threads:[~2010-02-04 11:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 11:31 Martin Jansa [this message]
2010-03-09 22:25 ` pointercal ignored? Ulf Samuelsson
2010-03-10 14:16 ` Marcin Juszkiewicz
2010-03-10 20:46 ` Ulf Samuelsson
2010-03-11 22:18 ` Ulf Samuelsson
2010-03-11 23:16 ` Koen Kooi
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=20100204113145.GR3401@jama \
--to=martin.jansa@gmail.com \
--cc=m.cavallini@koansoftware.com \
--cc=openembedded-devel@lists.openembedded.org \
/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.