Ticket #4260 (closed defect: fixed)
Mouse movement events sent after mouse clicks even if the mouse does not move -> fixed after 3.2.4
Reported by: | cortana | Owned by: | |
---|---|---|---|
Component: | guest additions | Version: | VirtualBox 3.2.4 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Windows |
Description
Related to the mouse movement issues I mentioned in #4086 the first comment: when I click a mouse button, the guest receives a button press/release event, followed immediately by a motion event, even though the mouse is not being moved.
The difference is that, now I'm using 2.2.4, the motion even occurs *after* the button events. This still results in annoying side-effects such as text being selected when clicking on a gnome-terminal window (since it thinks I just dragged the mouse pointer, I assume).
This can be observed in xev:
ButtonPress event, serial 33, synthetic NO, window 0x2000001, root 0x108, subw 0x0, time 4546735, (51,6), root:(421,441), state 0x10, button 1, same_screen YES MotionNotify event, serial 33, synthetic NO, window 0x2000001, root 0x108, subw 0x0, time 4546735, (51,6), root:(421,441), state 0x110, is_hint 0, same_screen YES ButtonRelease event, serial 33, synthetic NO, window 0x2000001, root 0x108, subw 0x0, time 4547431, (51,6), root:(421,441), state 0x110, button 1, same_screen YES MotionNotify event, serial 33, synthetic NO, window 0x2000001, root 0x108, subw 0x0, time 4547431, (51,6), root:(421,441), state 0x10, is_hint 0, same_screen YES
Running evtest on the input device corresponding to the mouse device only shows button events; the motion events are not present. If I remove the vboxmouse device from the X server then the spurious motion events go away, so I guess the problem lies there.
Change History
comment:1 Changed 14 years ago by michael
- Summary changed from Mouse movement events sent after mouse clicks even if the mouse does not move to Mouse movement events sent after mouse clicks even if the mouse does not move -> fixed in SVN
comment:2 Changed 14 years ago by cortana
Yup, this is fixed in 3.0.0, I guess it can be closed?
Thanks btw :)
comment:3 Changed 14 years ago by frank
- Status changed from new to closed
- Resolution set to fixed
Thanks for the feedback!
comment:4 Changed 13 years ago by cortana
- Status changed from closed to reopened
- Resolution fixed deleted
I am still seeing this with VirtualBox 3.2.0.
comment:5 Changed 13 years ago by frank
- Version changed from VirtualBox 2.2.4 to VirtualBox 3.2.4
Confirmed.
comment:6 Changed 13 years ago by michael
- Summary changed from Mouse movement events sent after mouse clicks even if the mouse does not move -> fixed in SVN to Mouse movement events sent after mouse clicks even if the mouse does not move -> fixed after 3.2.4
It should be squashed again now. Sorry about that.
Reproduced and fixed in SVN. The new code successfully passes on your testcase.