I cannot reproduce this with df_input either. I event tried adding a sleep in a few different places.
I figured out the problem. It is with my application. Sorry for the false alarm. I started down this road because a colleague of mine is experiencing a similar problem, but he is using X. Apparently the X driver for ELO has some problems... Thanks. Brandon Reynolds mailto:[EMAIL PROTECTED] Systems Engineer Ph: (330) 644-3059 Commercial Timesharing Inc. Fax: (330) 644-8110 > -----Original Message----- > From: Denis Oliver Kropp [mailto:[EMAIL PROTECTED] > Sent: Friday, December 19, 2003 6:22 AM > To: Brandon M. Reynolds > Cc: Directfb (E-mail) > Subject: Re: [directfb-dev] Input event problems > > > Quoting Brandon M. Reynolds: > > I've been working with an ELO touchscreen and a GTK+ > application. I noticed > > a problem where a touch event gets processed but it's > subsequent untouch > > event gets ignored. I confirmed that the driver is > dispatching the untouch. > > I'm not sure what the problem is exactly, but I 'fixed' it > by ensuring that > > there is at least 50ms between events. > > > > Does dfb_input_dispatch() some how end up ignoring events > until the current > > one is processed rather than queuing them up? Or is this a > problem with > > GTK+?? > > I can't reproduce this effect. dfb_input_dispatch() never drops any > event. Can you verify that with "df_input"? > > -- > Best regards, > Denis Oliver Kropp > > .------------------------------------------. > | DirectFB - Hardware accelerated graphics | > | http://www.directfb.org/ | > "------------------------------------------" > > Convergence GmbH > -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-dev" as subject.
