nanogui: Thread: 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

> 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?

Larry -

I assume you're running the nano-X API.  The GdReadMouse routine
is called in nanox/srvevents.c to queue up events from the lower level
driver into the nano-X event queue.  grep that file and put some debug
statements in the routine that calls devmouse.c::GdReadMouse()
and queues the events for the nano-X application.  IIRC this routine
is something like GsMouseEvent.  The GsMouseEvent routine is
called from the upper level main loop in nanox/srvmain.c::GsSelect()
when it is notified that there is new mouse data.  GsMouseEvent
then calls GdReadMouse and the mou_touchscreen driver entry point.

Regards,

Greg