Re: [PATCH 1/1] evdev: Wait for SYN event before sending events over to the client

2013-03-02 Thread Bill Spitzak
On 02/22/2013 10:56 AM, Singh, Satyeshwar wrote: + if (!device->pending_events || !(device->pending_events & EVDEV_SYN)) This is the same as: if (!(device->pending_events & EVDEV_SYN)) (ie all the other bits in pending_events are ignored). is this correct? __

Re: [PATCH 1/1] evdev: Wait for SYN event before sending events over to the client

2013-02-27 Thread Kristian Høgsberg
On Sat, Feb 23, 2013 at 11:50:34AM +0100, Jonas Ådahl wrote: > Hi, > > On Fri, Feb 22, 2013 at 7:56 PM, Singh, Satyeshwar > wrote: > > The issue was that touch::down event from the compositor to client apps > > would send the previous motion events coordinates and this obviously made > > the clie

Re: [PATCH 1/1] evdev: Wait for SYN event before sending events over to the client

2013-02-23 Thread Jonas Ådahl
Hi, On Fri, Feb 22, 2013 at 7:56 PM, Singh, Satyeshwar wrote: > The issue was that touch::down event from the compositor to client apps > would send the previous motion events coordinates and this obviously made > the client do the wrong thing. This happened because we were not waiting for > a SY

[PATCH 1/1] evdev: Wait for SYN event before sending events over to the client

2013-02-22 Thread Singh, Satyeshwar
The issue was that touch::down event from the compositor to client apps would send the previous motion events coordinates and this obviously made the client do the wrong thing. This happened because we were not waiting for a SYN event to come from evdev before sending down, motion or up events. Th