nanogui: Thread: Touch screen problem

Hi,

I use H3600_ts in Assabet, but it works sometimes for microwindows,
sometimes not.  Why?

Raymond

Hi Greg,

Following the pattern of mou_serial.c, I've developed a nano-X driver
for two serial/PS2 touchscreens: an Usar Touch and a MicroTouch. 

They work fine, the only problem is that often a finger-up event is
is lost by nano-X (not by the driver, I've checked out this). 

How can this irritating problem be solved?

BTW, based on Bradley D. LaRonde calibration program for Microwindows, I
have developed a similar application for nano-X. However, because of the
client/server architecture of a typical nano-X application, I had to do
a simple hack on the nano-X source in order to prevent it to do
coordinate transformation when calibrating.

Greg, if you are interested I can send you the source of the two
touchscreens drivers and of the calibration application.

Thanks in advance

Gianci -

When you get your last event from the controller (basically, saying that the 
button was released), you are setting the button state to be 0 and returning 
2, correct from Mou_Read(), correct?

Jordan

On Wednesday 14 November 2001 09:30, Gianci mentioned:
> Hi Greg,
>
> Following the pattern of mou_serial.c, I've developed a nano-X driver
> for two serial/PS2 touchscreens: an Usar Touch and a MicroTouch.
>
> They work fine, the only problem is that often a finger-up event is
> is lost by nano-X (not by the driver, I've checked out this).
>
> How can this irritating problem be solved?
>
> BTW, based on Bradley D. LaRonde calibration program for Microwindows, I
> have developed a similar application for nano-X. However, because of the
> client/server architecture of a typical nano-X application, I had to do
> a simple hack on the nano-X source in order to prevent it to do
> coordinate transformation when calibrating.
>
> Greg, if you are interested I can send you the source of the two
> touchscreens drivers and of the calibration application.
>
> Thanks in advance
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####

On Wednesday 14 November 2001 09:42, Jordan Crouse wrote:

> When you get your last event from the controller (basically, saying
> that the button was released), you are setting the button state to be
> 0 and returning 2, correct from Mou_Read(), correct?

Yes, that's correct, but it seems that the problem is not in my driver.

Note that if the Microtouch TS is configured in up-down mode, that is,
sending an event only when the TS is pressed or released, that all is
OK. If it is configured in stream mode, that is, sending a continuous
stream of events while the TS is pressed, then the problem arises. 

Regards,
Gianci

Hi,
I am working with strongarm based custom design board. I am using
linux-2.4.13 version. We r using wm9705 chip for touch scrren. So I have
modify the ucb1x00_ts.c driver for wm9705 chip and i am getting x, y
coordinate. But I am not able to integarate this with micrwindows. I am
using microwindows-0.89 version. I have selected mou_ipaq.c in my
configuration. Is it ok. But whenever i m touching the screen, i am not
getting anything. I am using major amd minor no. 10 & 14 respectively.
If i use 10 and 0 then i am getting an error error 19 cannot open touch
panel and cannot initialize mouse.

So can you suggest me where I am doing wrong.

One more thing. Whenever i run nano-X and after that if i run nanowm the
i m getting the error
[1]+  Stopped (tty output)    ./nano-X 

Why is it so? 
But I can see the demo on my LCD screen.

Waiting for ur reply....

Thanks & Regards.....

Rakesh