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 _______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
