nanogui: Thread: Re: nanogui Digest 22 Jul 2011 23:34:15 -0000 Issue 1694

Hi,
I attach a patch with an updated driver and keyboard events driver.
Now they autodetect the first available event driver of the correct kind.
I tested them with microwindows 0.92. They should work also with nano-X +
nxlib + fltk.
Please note that this driver is a much simpler (and less powerful)
alternative to tslib. Unlike tslib it doesn't provide filtering nor
decimation, so the source must generate clean events. The good thing is that
it's already integrated with mw.
This patch includes also some other minor corrections to mw code.
Any feedback/opinion is welcome
Davide Rizzo

2011/7/23 ####@####.####

>
> nanogui Digest 22 Jul 2011 23:34:15 -0000 Issue 1694
>
> Topics (messages 13055 through 13055)
>
> microwindows touch screen using input event0 not working
>        13055 by: Larry Samuels
>
> Administrivia:
>
> To subscribe to the digest, e-mail:
>        ####@####.####
>
> To unsubscribe from the digest, e-mail:
>        ####@####.####
>
> To post to the list, e-mail:
>        ####@####.####
>
>
> ----------------------------------------------------------------------
>
>
>
> ---------- Messaggio inoltrato ----------
> From: Larry Samuels ####@####.####
> To: ####@####.#### ####@####.####
> Date: Fri, 22 Jul 2011 19:31:47 -0400
> Subject: microwindows touch screen using input event0 not working
> Hello,
>  I am porting microwindows to an embedded system, and I am trying to get
> the touchscreen to be read from microwindows demo apps.
>  I am  using a patched file on microwindows v 0.92 to connect the
> /dev/input/event0 to microwindows.
> The patch is from:
> http://www.linuxhacker.org/cgi-bin/ezmlm-cgi?5:msn:10843
> I can run microwindows apps on the target with debug info printed to the
> console.
> I see mouse touch events coming from mou_event.c (the new driver instead of
> mou_touchscreen.c).
> I see mouse touch events coming from devmouse.c  (GrReadMouse displays new
> x,y positions).
> But, nxcal, nxscribble do not show any mouse events or movement.
> Can you help me troubleshoot how to get applications to see the mouse
> position, when the engine sees it?
> My target is Samsung S3C2440 ARM9 processor with built in touch sensor.
>
> Regards,
> Larry Samuels
>
>


-- 
All difficult problems have a simple solution. That is wrong. [A. Einstein]

Davide -

Looks good. Are you saying that Larry's problem was that
the upper level didn't properly handle reading the mouse
driver with the proper event, while this driver does?

Regards,

Greg


: Hi,
: I attach a patch with an updated driver and keyboard events driver.
: Now they autodetect the first available event driver of the correct kind.
: I tested them with microwindows 0.92. They should work also with nano-X +
: nxlib + fltk.
: Please note that this driver is a much simpler (and less powerful)
: alternative to tslib. Unlike tslib it doesn't provide filtering nor
: decimation, so the source must generate clean events. The good thing is 
that
: it's already integrated with mw.
: This patch includes also some other minor corrections to mw code.
: Any feedback/opinion is welcome
: Davide Rizzo
:
: 2011/7/23 ####@####.####
:
: >
: > nanogui Digest 22 Jul 2011 23:34:15 -0000 Issue 1694
: >
: > Topics (messages 13055 through 13055)
: >
: > microwindows touch screen using input event0 not working
: >        13055 by: Larry Samuels
: >
: > Administrivia:
: >
: > To subscribe to the digest, e-mail:
: >        ####@####.####
: >
: > To unsubscribe from the digest, e-mail:
: >        ####@####.####
: >
: > To post to the list, e-mail:
: >        ####@####.####
: >
: >
: > ----------------------------------------------------------------------
: >
: >
: >
: > ---------- Messaggio inoltrato ----------
: > From: Larry Samuels ####@####.####
: > To: ####@####.#### ####@####.####
: > Date: Fri, 22 Jul 2011 19:31:47 -0400
: > Subject: microwindows touch screen using input event0 not working
: > Hello,
: >  I am porting microwindows to an embedded system, and I am trying to get
: > the touchscreen to be read from microwindows demo apps.
: >  I am  using a patched file on microwindows v 0.92 to connect the
: > /dev/input/event0 to microwindows.
: > The patch is from:
: > http://www.linuxhacker.org/cgi-bin/ezmlm-cgi?5:msn:10843
: > I can run microwindows apps on the target with debug info printed to the
: > console.
: > I see mouse touch events coming from mou_event.c (the new driver instead 
of
: > mou_touchscreen.c).
: > I see mouse touch events coming from devmouse.c  (GrReadMouse displays 
new
: > x,y positions).
: > But, nxcal, nxscribble do not show any mouse events or movement.
: > Can you help me troubleshoot how to get applications to see the mouse
: > position, when the engine sees it?
: > My target is Samsung S3C2440 ARM9 processor with built in touch sensor.
: >
: > Regards,
: > Larry Samuels
: >
: >
:
:
: -- 
: All difficult problems have a simple solution. That is wrong. [A. 
Einstein]
:


--------------------------------------------------------------------------------


:
: ---------------------------------------------------------------------
: To unsubscribe, e-mail: ####@####.####
: For additional commands, e-mail: ####@####.#### 

Examinating Larry's report, my suspect is that some touchscreen drivers
report pressure as EV_KEY BTN_TOUCH, while other ones report EV_ABS
ABS_PRESSURE.
My driver manages only the first one, but it's very easy to add 3 lines of
code to manage also the second one.
I don't agree on Larry's modifies on devmouse.c, calibration should be
performed at higher levels by nxcal.
Regards
Davide Rizzo


2011/7/26 Greg Haerr ####@####.####

> Davide -
>
> Looks good. Are you saying that Larry's problem was that
> the upper level didn't properly handle reading the mouse
> driver with the proper event, while this driver does?
>

Regards,
>
> Greg
>