Re: winex11.drv: don't drop raw input events after mouse warp

[Alexandre Julliard]

Patrick Rudolph  writes:
> I've attached a log file, here:
> https://bugs.winehq.org/attachment.cgi?id=50258
> As you can see XWarpCursor inserts MotionNotify events, that are
> correctly ignored using the serial, but there're no inserted RawMotion
> events. So there's no need to drop them, correct me if I'm
> wrong. Sadly I couldn't find any documentation for XWarpCursor and
> RawMotion events.

That's the way it's supposed to behave, but sadly that's not true on all
systems, that's why I had to add that hack.