nanogui: Thread: touch screen


[<<] [<] Page 1 of 2 [>] [>>]
Subject: touch screen
From: victor ####@####.####
Date: 14 Aug 2001 21:27:47 -0000
Message-Id: <3B7997B7.59BF644@aaeon.com>

Hi, 
I am using a touch screen(DYNAPRO 95659) connected to my arm board to
access microwindows. Do you know which driver in microwindows should I
choose? Or where in the driver files of microwindows should I change?
I got a mouse error everytime I touch my screen. 
But if I change the ipaq mouse driver a little bit, I can still access
the window with some kind of "shrinking" mapping so I am sure it should
be able to work with correct touch screen driver on microwindow.
Do you have any ideas, thanks??

vic
Subject: Re: [nanogui] touch screen
From: Jordan Crouse ####@####.####
Date: 14 Aug 2001 21:36:17 -0000
Message-Id: <01081415363205.01580@cosmic>

There are generally two types of Strongarm touchscreens.  Most strongarm 
devices (I would say probably about 80%) use the UCB1x00 (usually the 
UCB1200).  For these devices, use the ADSMOUSE.  I have only seen one 
Strongarm device that does not use the UCB1x00, and thats the Ipaq.  Alot of 
it depends on which touchscreen drivery you use in the kernel.  If you use 
the h3600_ts driver, then use IPAQMOUSE, otherswise if you use ucb1200_ts,
then use ADSMOUSE.

Jordan
 
On Tuesday 14 August 2001 15:27, victor mentioned:
> Hi,
> I am using a touch screen(DYNAPRO 95659) connected to my arm board to
> access microwindows. Do you know which driver in microwindows should I
> choose? Or where in the driver files of microwindows should I change?
> I got a mouse error everytime I touch my screen.
> But if I change the ipaq mouse driver a little bit, I can still access
> the window with some kind of "shrinking" mapping so I am sure it should
> be able to work with correct touch screen driver on microwindow.
> Do you have any ideas, thanks??
>
> vic
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
Subject: Re: [nanogui] touch screen
From: victor ####@####.####
Date: 15 Aug 2001 16:04:59 -0000
Message-Id: <3B7A9D92.312E8EBD@aaeon.com>

Hi,
I found out that if I change the screen_width and height in config, I
can get a resonable position on my screen using mou_ipaq driver. But I
have a problem that the "click" event is not very cleanly recongnize.
It's very hard for me to close the pop up window when I click the x spot
on the upper-right of the window. Do you have any idea to fix it??

And should I do the calibration? or just change the screen width and
height setting for the correct position.

thank you.


Jordan Crouse wrote:
> 
> There are generally two types of Strongarm touchscreens.  Most strongarm
> devices (I would say probably about 80%) use the UCB1x00 (usually the
> UCB1200).  For these devices, use the ADSMOUSE.  I have only seen one
> Strongarm device that does not use the UCB1x00, and thats the Ipaq.  Alot of
> it depends on which touchscreen drivery you use in the kernel.  If you use
> the h3600_ts driver, then use IPAQMOUSE, otherswise if you use ucb1200_ts,
> then use ADSMOUSE.
> 
> Jordan
> 
> On Tuesday 14 August 2001 15:27, victor mentioned:
> > Hi,
> > I am using a touch screen(DYNAPRO 95659) connected to my arm board to
> > access microwindows. Do you know which driver in microwindows should I
> > choose? Or where in the driver files of microwindows should I change?
> > I got a mouse error everytime I touch my screen.
> > But if I change the ipaq mouse driver a little bit, I can still access
> > the window with some kind of "shrinking" mapping so I am sure it should
> > be able to work with correct touch screen driver on microwindow.
> > Do you have any ideas, thanks??
> >
> > vic
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ####@####.####
> > For additional commands, e-mail: ####@####.####
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
Subject: Re: [nanogui] touch screen
From: Jordan Crouse ####@####.####
Date: 15 Aug 2001 16:08:38 -0000
Message-Id: <01081510085007.21329@cosmic>

If you are getting mouse clicks then you are using the correct driver.  Now 
you definately need to calibrate to get accurate button clicks  There are 
several calibration programs available, check www.handhelds.org for more info.

Jordan

On Wednesday 15 August 2001 10:04, victor mentioned:
> Hi,
> I found out that if I change the screen_width and height in config, I
> can get a resonable position on my screen using mou_ipaq driver. But I
> have a problem that the "click" event is not very cleanly recongnize.
> It's very hard for me to close the pop up window when I click the x spot
> on the upper-right of the window. Do you have any idea to fix it??
>
> And should I do the calibration? or just change the screen width and
> height setting for the correct position.
>
> thank you.
>
> Jordan Crouse wrote:
> > There are generally two types of Strongarm touchscreens.  Most strongarm
> > devices (I would say probably about 80%) use the UCB1x00 (usually the
> > UCB1200).  For these devices, use the ADSMOUSE.  I have only seen one
> > Strongarm device that does not use the UCB1x00, and thats the Ipaq.  Alot
> > of it depends on which touchscreen drivery you use in the kernel.  If you
> > use the h3600_ts driver, then use IPAQMOUSE, otherswise if you use
> > ucb1200_ts, then use ADSMOUSE.
> >
> > Jordan
> >
> > On Tuesday 14 August 2001 15:27, victor mentioned:
> > > Hi,
> > > I am using a touch screen(DYNAPRO 95659) connected to my arm board to
> > > access microwindows. Do you know which driver in microwindows should I
> > > choose? Or where in the driver files of microwindows should I change?
> > > I got a mouse error everytime I touch my screen.
> > > But if I change the ipaq mouse driver a little bit, I can still access
> > > the window with some kind of "shrinking" mapping so I am sure it should
> > > be able to work with correct touch screen driver on microwindow.
> > > Do you have any ideas, thanks??
> > >
> > > vic
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: ####@####.####
> > > For additional commands, e-mail: ####@####.####
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ####@####.####
> > For additional commands, e-mail: ####@####.####
Subject: Re: [nanogui] touch screen
From: victor ####@####.####
Date: 15 Aug 2001 18:42:35 -0000
Message-Id: <3B7AC27D.514CE517@aaeon.com>

Hi, I run the tpcal in the microwin's contrib directory for calibration
and get 7 numbers. But do you know where should I set for these 7
numbers?? 
I don't see mou_ipaq driver try to read a calibration data in
initialization while some other touch screen drivers (mou_tp.c,
mou_yopy.c) did using function "GetPointerCalibrationData()".

thanks

Jordan Crouse wrote:
> 
> If you are getting mouse clicks then you are using the correct driver.  Now
> you definately need to calibrate to get accurate button clicks  There are
> several calibration programs available, check www.handhelds.org for more info.
> 
> Jordan
>
Subject: RE: [nanogui] touch screen
From: Simon Wood ####@####.####
Date: 16 Aug 2001 08:43:29 -0000
Message-Id: <44632C76B97BD211AF6B00805FADCAB2087907C3@exchange.saltaire.pace.co.uk>

> -----Original Message-----
> From:	victor ####@####.####
> Sent:	Wednesday, August 15, 2001 7:42 PM
> To:	####@####.####
> Cc:	####@####.####
> Subject:	Re: [nanogui] touch screen
> 
> Hi, I run the tpcal in the microwin's contrib directory for calibration
> and get 7 numbers. But do you know where should I set for these 7
> numbers?? 
	[Simon Wood]  
	The Linux-VR demos stick these magic numbers in 
	/etc/pointercal, I assume that this file is read 
	when the touch screen driver is initialised.

	I'm also seeing some in-accuracies is position, 
	getting worse towards the top/right, when using the
	R rotated screen - though normal (no rotation) works
	well. Anyone else seen this??

> I don't see mou_ipaq driver try to read a calibration data in
> initialization while some other touch screen drivers (mou_tp.c,
> mou_yopy.c) did using function "GetPointerCalibrationData()".
> 
Subject: Re: [nanogui] touch screen
From: "Greg Haerr" ####@####.####
Date: 16 Aug 2001 19:41:13 -0000
Message-Id: <070401c12688$a3672c20$6817dbd0@censoft.com>

: I'm also seeing some in-accuracies is position, 
: getting worse towards the top/right, when using the
: R rotated screen - though normal (no rotation) works
: well. Anyone else seen this??
: 
: > I don't see mou_ipaq driver try to read a calibration data in
: > initialization while some other touch screen drivers (mou_tp.c,
: > mou_yopy.c) did using function "GetPointerCalibrationData()".

It sounds like too many people are having problems getting
the screen calibrated for Microwindows.  I suggest that I have
Century Software release the source code to their touch screen
calibrator for Microwindows, and include it in the standard
distribution.  I'm not aware of any problems with it.  It's currently
available for the iPAQ, ADS, and a few other systems.

Comments?

Regards,

Greg

Subject: Re: [nanogui] touch screen
From: "Greg Haerr" ####@####.####
Date: 16 Aug 2001 19:41:18 -0000
Message-Id: <07b901c1268a$c84e1fb0$6817dbd0@censoft.com>

Victor,
    I'll have someone over here work on getting it together.
Unfortunately, we're all busy as hell for the LW tradeshow
coming up, so it will likely be several days.  When I get it,
I'll send it to you.

Regards,

Greg

: The sooner the better.
: 
: thanks
: 
: Greg Haerr wrote:
: 
: > It sounds like too many people are having problems getting
: > the screen calibrated for Microwindows.  I suggest that I have
: > Century Software release the source code to their touch screen
: > calibrator for Microwindows, and include it in the standard
: > distribution.  I'm not aware of any problems with it.  It's currently
: > available for the iPAQ, ADS, and a few other systems.
: > 
: > Comments?
: > 
: > Regards,
: > 
: > Greg

Subject: Re: [nanogui] touch screen
From: "Kevin" ####@####.####
Date: 17 Aug 2001 07:16:37 -0000
Message-Id: <000f01c126ea$3101f860$11e36ad2@hanq>

If you need some help, I suggest this one.

I tested this code on Yopy with landscape mode and worked fine. I am not
sure that it will work any other
touch pannel(ie Ipaq's ).

Kevin.

----- Original Message -----
From: "Greg Haerr" ####@####.####
To: "Simon Wood" ####@####.#### "'victor'" ####@####.####
Cc: ####@####.####
Sent: Friday, August 17, 2001 4:21 AM
Subject: Re: [nanogui] touch screen


>
> : I'm also seeing some in-accuracies is position,
> : getting worse towards the top/right, when using the
> : R rotated screen - though normal (no rotation) works
> : well. Anyone else seen this??
> :
> : > I don't see mou_ipaq driver try to read a calibration data in
> : > initialization while some other touch screen drivers (mou_tp.c,
> : > mou_yopy.c) did using function "GetPointerCalibrationData()".
>
> It sounds like too many people are having problems getting
> the screen calibrated for Microwindows.  I suggest that I have
> Century Software release the source code to their touch screen
> calibrator for Microwindows, and include it in the standard
> distribution.  I'm not aware of any problems with it.  It's currently
> available for the iPAQ, ADS, and a few other systems.
>
> Comments?
>
> Regards,
>
> Greg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####

[Content type application/octet-stream not shown. Download]
Subject: Touchscreen
From: ####@####.####
Date: 16 May 2004 19:36:16 +0100
Message-Id: <33749.209.103.193.29.1084732573.squirrel@webmail.athenet.net>

Which source file is in charge of starting the touch screen? I found the
file that actually opens the /dev/ts device (moutouchscreen.c), but which
file calls that file? For some reason, that method isn't being called.

Thanks,

Adam Ernst
cosmicsoft
[<<] [<] Page 1 of 2 [>] [>>]


Powered by ezmlm-browse 0.20.