What's happening to DeviceMotionNotifies?

[Daniel Stone]

On Thu, Nov 30, 2006 at 01:54:53PM +1030, Peter Hutterer wrote:
> a print of event in _XEnq  gives me an event with opcode 83.
> 
> (gdb) p event->u.keyButtonPointer
> $3 = {pad00 = 852051, time = 916675313, root = 93, event = 2097153,  
> child = 0, rootX = 512, rootY = 384, eventX = 505, eventY = 377,  
> state = 0,  sameScreen = 1 '\001', pad1 = 2 '\002'}
> 
> looks about alright to me. pad1 for extension events is the deviceID  
> AFAIK, which is 2 and correct.
> 
> XInputToWire copies the data correctly but returns DONT_ENQUEUE (0),  
> so the event is "ignored, or stashed away for many-to-one  
> compression" (comment in the source). As far as I can tell, that  
> happens to all events. _XReadEvents() never exits.
> 
> 
> does that help?

Yeah, it does, thanks.  Looking at the lib, it's immediately obvious
why: it always enqueues DeviceMotionNotify events, in the hope of
getting a DeviceValuator event straight after, in spite of the
MORE_EVENTS flag not being set.  Thanks, libXi.

I've pushed a fix for this to master.

> There are no DeviceValuator events. I'm using standard mice so they  
> wouldn't send ones, would they?

You'd think not ...

Cheers,
Daniel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.x.org/archives/xorg/attachments/20061206/db90b32d/attachment.pgp>