nanogui: Thread: Problem with event BUTTON UP

Hi, 

I'm working with M5329EVB and a display kit with touchscreen. The touch is working fine, the co-ordinate returned are quiet OK. However, when I press the screen on a child window for more than 1 second, the event BUTTON UP returned shows subwid is parent window and wid is also parent but that is normal... and if I press the screen quickly, I have the correct child  window id in subwid. Is there any configuration about that ?

Thanks,
William,

> I'm working with M5329EVB and a display kit with touchscreen. The touch is 
> working fine, the co-ordinate returned are quiet OK. However, when I press 
> the screen on a child window for more than 1 second, the event BUTTON UP 
> returned shows subwid is parent window and wid is also parent but that is 
> normal... and if I press the screen quickly, I have the correct child 
> window id in subwid. Is there any configuration about that ?


This is a bit strange.  Can you test this using a simple program
on the desktop with a mouse rather than touchscreen?  I
want to know whether this is related to touchscreen jitter,
or a timing issue with the mouse up event after mouse down.

You might look at the code in nanox/srvevent.c and srvutil.c
to see how mouse events are handled and the child window
id calculated.  Some debug/printf statements in that area
may also help, to see whether the up event has the same coordinates
as the down, for instance.

Regards,

Greg