Fwd: [PATCH 3/3] evdev: Don't post REL_MISC events as axis motion. (#24737)

[Bartosz Brachaczek]

2010/8/17 Peter Hutterer <peter.hutterer at who-t.net>:
> On Mon, Aug 16, 2010 at 12:50:16PM +0200, Bartosz Brachaczek wrote:
>> The problem is that the X server still posts MotionNotify events
>> because of these REL_MISC events, which according to libX11 specs
>> (section 10.5.2) is incorrect because MotionNotify indicates that the
>> pointer moved, which isn't the case here. So either evdev should not
>> post REL_MISC as a motion event or X server should check if the
>> pointer actually moved before posting MotionNotify event.
>
> this is a server bug, but afaict not much of an issue at this point, I don't
> know of an application that screws up because it gets two MotionNotifies
> with the same x/y coordinates. If there is one that would up the priority a
> bit but this bug has been around since at least 1.7.
>
> http://bugs.freedesktop.org/show_bug.cgi?id=23985
>
> Cheers,
>  Peter
>

Actually some KDE elements get confused and act incorrectly because of
getting a MotionNotify between ButtonPress and ButtonRelease when the
user didn't move his device. It is very annoying and it's described in
bug #24737, comment 29:
http://bugs.freedesktop.org/show_bug.cgi?id=24737#c29

Cheers,
Bartosz