Its based on how the code, as left to me by a previous developer, works.  Architecturally it was cumbersome and highly dependent on GetXY functioning.  (e.g. the events were consumed in one portion of the code that signaled a different portion of code that relied on GetXY)

We have resolved this by looking at the events and pulling out the axis information, etc.  If the GetXY functioned for us we wouldn't have had to modify anything.

Thank you,

Gavin Stark


On Oct 4, 2005, at 3:22 PM, Ville Syrjälä wrote:

On Mon, Oct 03, 2005 at 05:38:10PM -0400, Gavin Stark - RDM wrote:


We have been successfully using a touch panel via DirectFB-0.9.20 -   
Now using DirectFB-0.9.22 we are having problems receiving input  
events.   We had been utilizing CreateEventBuffer on the mouse input  
device and then calling GetXY whenever we see an appropriate event.    


Umm, why do you use GetXY() when the event already gives you the 
information needed?

-- 
Ville Syrjälä


_______________________________________________
directfb-dev mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev

Reply via email to