MotionNotify collapsing keeps the first event instead of last

Bug #1728870 reported by Samuel thibault
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Compiz
Fix Released
Undecided
Unassigned

Bug Description

Hello,

While working on XInput2 support, I noticed a small bug on collapsing MotionNotify events: the code was actually returning the first MotionNotify instead of the last one. This probably brings some small glitches which went not reported because not too bad, but still an inconvenience for users.
In merge request https://code.launchpad.net/~samuel-thibault/compiz/motion-dup-fix/+merge/332871 I fix this into keeping the last one.

Samuel

Related branches

Revision history for this message
Dmitry Shachnev (mitya57) wrote :

Compiz 0.9.14.0 was released today, which includes this fix.

Changed in compiz:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.