On Tue, Mar 20, 2012 at 09:36:33PM -0700, Chase Douglas wrote:
> On 03/20/2012 05:02 PM, Kristian Hoegsberg wrote:
> > On Tue, Mar 20, 2012 at 11:54:56AM +0200, Ander Conselvan de Oliveira wrote:
> >> When the compositor is in a repaint cycle, input is processed only once
> >> per frame. However, a
On 03/20/2012 05:02 PM, Kristian Hoegsberg wrote:
> On Tue, Mar 20, 2012 at 11:54:56AM +0200, Ander Conselvan de Oliveira wrote:
>> When the compositor is in a repaint cycle, input is processed only once
>> per frame. However, a call to evdev_input_device_data() would handle at
>> most 8 events at
On Tue, Mar 20, 2012 at 11:54:56AM +0200, Ander Conselvan de Oliveira wrote:
> When the compositor is in a repaint cycle, input is processed only once
> per frame. However, a call to evdev_input_device_data() would handle at
> most 8 events at time. When there was more than 8 events pending for a
>
On 03/20/2012 06:54 AM, Ander Conselvan de Oliveira wrote:
When the compositor is in a repaint cycle, input is processed only once
per frame. However, a call to evdev_input_device_data() would handle at
most 8 events at time. When there was more than 8 events pending for a
given frame, input lag
When the compositor is in a repaint cycle, input is processed only once
per frame. However, a call to evdev_input_device_data() would handle at
most 8 events at time. When there was more than 8 events pending for a
given frame, input lag would occur. This was most visible with multi
touch input.
T
