Re: [PATCH] Don't report old relative values in getValuatorEvents

2011-04-06 Thread Chase Douglas
On 04/05/2011 07:31 PM, Jeremy Huddleston wrote: (related to my recent reply for the 1.10 merge of this patch) I believe this should this instead be: +else if (dev dev-valuator-axes[xv-first_valuator + j].mode == Absolute) As much as I just want to be done with this issue, I

Re: [PATCH] Don't report old relative values in getValuatorEvents

2011-04-05 Thread Jeremy Huddleston
(related to my recent reply for the 1.10 merge of this patch) I believe this should this instead be: +else if (dev dev-valuator-axes[xv-first_valuator + j].mode == Absolute) On Mar 31, 2011, at 08:29, Chase Douglas wrote: Relative valuator values should not be reported in any

Re: [PATCH] Don't report old relative values in getValuatorEvents

2011-04-03 Thread Peter Hutterer
On Thu, Mar 31, 2011 at 11:29:01AM -0400, Chase Douglas wrote: Relative valuator values should not be reported in any future events. If a relative valuator value is not set in an internal event, set the value to 0 for XI 1.x valuator events sent over the wire. Signed-off-by: Chase Douglas

Re: [PATCH] Don't report old relative values in getValuatorEvents

2011-04-01 Thread Simon Thum
On 03/31/2011 05:29 PM, Chase Douglas wrote: Relative valuator values should not be reported in any future events. If a relative valuator value is not set in an internal event, set the value to 0 for XI 1.x valuator events sent over the wire. Signed-off-by: Chase Douglas

[PATCH] Don't report old relative values in getValuatorEvents

2011-03-31 Thread Chase Douglas
Relative valuator values should not be reported in any future events. If a relative valuator value is not set in an internal event, set the value to 0 for XI 1.x valuator events sent over the wire. Signed-off-by: Chase Douglas chase.doug...@canonical.com --- dix/eventconvert.c |4 +++- 1