Re: [PATCH weston 1/3] eventdemo: do not print pointer frames alone

2016-05-13 Thread Pekka Paalanen
On Fri, 13 May 2016 11:03:07 +0200 Benoit Gschwind wrote: > Hello Pekka, > > as-is you get my: > Reviewed-by: Benoit Gschwind > Tested-by: Benoit Gschwind > > But I have comments that may be worth to read :) > > On 10/05/2016 16:11, Pekka Paalanen wrote: > > From: Pekka Paalanen > > > > Pr

Re: [PATCH weston 1/3] eventdemo: do not print pointer frames alone

2016-05-13 Thread Benoit Gschwind
Hello Pekka, as-is you get my: Reviewed-by: Benoit Gschwind Tested-by: Benoit Gschwind But I have comments that may be worth to read :) On 10/05/2016 16:11, Pekka Paalanen wrote: > From: Pekka Paalanen > > Print pointer frames only if any pointer related events are printed > first. > > This

Re: [PATCH weston 1/3] eventdemo: do not print pointer frames alone

2016-05-10 Thread Yong Bakos
On May 10, 2016, at 9:11 AM, Pekka Paalanen wrote: > > From: Pekka Paalanen > > Print pointer frames only if any pointer related events are printed > first. > > This avoids flooding the output with "pointer frame" just because of > motion. > > Signed-off-by: Pekka Paalanen A suggestion rega

Re: [PATCH weston 1/3] eventdemo: do not print pointer frames alone

2016-05-10 Thread Yong Bakos
On May 10, 2016, at 9:11 AM, Pekka Paalanen wrote: > > From: Pekka Paalanen > > Print pointer frames only if any pointer related events are printed > first. > > This avoids flooding the output with "pointer frame" just because of > motion. > > Signed-off-by: Pekka Paalanen Makes sense, even

[PATCH weston 1/3] eventdemo: do not print pointer frames alone

2016-05-10 Thread Pekka Paalanen
From: Pekka Paalanen Print pointer frames only if any pointer related events are printed first. This avoids flooding the output with "pointer frame" just because of motion. Signed-off-by: Pekka Paalanen --- clients/eventdemo.c | 26 ++ 1 file changed, 26 insertions(+)