VirtualBox

Ticket #8331 (new defect)

Opened 3 years ago

Last modified 9 months ago

Mouse tracking fails on dual screen (when not using Mouse Integration)

Reported by: gslender Owned by:
Priority: major Component: GUI
Version: VirtualBox 4.0.2 Keywords: dual screen mouse
Cc: Guest type: Linux
Host type: Windows

Description (last modified by klaus) (diff)

Using latest version of VB (4.0.2) and Windows 7

When VB window is placed on a non-primary desktop part of a dual screen (in my case, to the right extended desktop) the mouse tracking is all wrong/fails. This only happens for guests where Mouse Integration is not an option or enabled. The mouse tracking doesn't work and essentially the VM Windows is unusable in dual screen setups (like mine). The tracking events are stuffed up and the mouse is pushed as if back onto the primary desktop (when obviously you are in the window of VB in the secondary desktop/screen).

Change History

comment:1 Changed 3 years ago by Dave_Scream

Im have windows 7 host and Windows XP guest this bug works too...

on version 4.0.4 the bug exixts too

How to make it: 1.Get dual screen system 2.Open Vbox in fullscreen on secondary (not primary) monitor 3.Switch off mouse integration mode 4.Go mouse pointer to all 4 directions 5.U'll see that guest machine lost mouse pointer focus no matter that integration mode is switched off

comment:2 Changed 3 years ago by osterac

I also have this problem. At first I thought it was related to the fact that my monitors are set to different resolutions, but after changing them to matching resolutions the problem remained. With older versions of virtualbox, I could not drag VM windows from one screen to the next without them snapping to the bottom of the screen and spasming. It still does this if I change the resolution while virtualbox is open. Windows 7 x64 host with Windows XP, Windows Vista, and Windows 98 guests.

comment:3 Changed 3 years ago by nicorac

Same here, my setup:

Host: Windows7 x64 Pro
VBox: 4.1.0
Secondary screen at left side (it has negative coordinates)
Mouse integration does not affect, bug always present

comment:4 Changed 3 years ago by tomxp411

Also seeing it on Windows7 x64 Ultimate host with a WS2008 guest. VBox 4.1.2 Secondary screen is to the left of the main monitor. Happens when pointer integration is turned off.

If I move the mouse up, for example, the cursor suddenly un-captures itself. The host cursor will be at the top of the physical monitor, and the guest cursor will be somewhere in the middle of the virtual monitor.

It looks like VBox is passing the relative mouse movement in to the guest but not moving the mouse cursor back to a fixed position.

I have written a remote control app, and here's what I came up with as the best way to deal with it:

  1. When clicking on the guest window, hide the HOST mouse cursor.
  2. Remember the host's mouse position.
  3. Move the HOST mouse cursor to the center of the display.
  4. When the mouse moves, grab the new mouse coordinates. Calculate the offset from the center of the display. Pass that in to the guest mouse driver as a relative movement. (Never absolutely position the guest cursor.)
  5. Move the HOST mouse BACK to the center of the display.

When the user presses the host key:

  1. Release the cursor from the guest.
  2. Move the host cursor back to the remembered position.
  3. Show the host cursor.

comment:5 follow-up: ↓ 7 Changed 14 months ago by DonGateley

Still true on 4.2.6 so I guess there is no interest among the developers to fix this. Heavy sigh.

comment:6 Changed 14 months ago by nicorac

That's really sad, because multimonitor configurations are getting widespread.

comment:7 in reply to: ↑ 5 ; follow-up: ↓ 8 Changed 14 months ago by klaus

  • Description modified (diff)

Replying to DonGateley:

Still true on 4.2.6 so I guess there is no interest among the developers to fix this. Heavy sigh.

Your guess is plain wrong. Please bear in mind that you're not the only person using VirtualBox (many million users, and quite some other bug reports), and this implies that the developers have to prioritize issues.

Disabling mouse integration is a VERY unusual setup, only a tiny fraction of the user base even knows that this is an option.

comment:8 in reply to: ↑ 7 Changed 9 months ago by Joe E. S.

Replying to klaus:

Replying to DonGateley:

Still true on 4.2.6 so I guess there is no interest among the developers to fix this. Heavy sigh.

Your guess is plain wrong. Please bear in mind that you're not the only person using VirtualBox (many million users, and quite some other bug reports), and this implies that the developers have to prioritize issues.

Disabling mouse integration is a VERY unusual setup, only a tiny fraction of the user base even knows that this is an option.

As far as developers having limited time, a ton of bugs to fix, and thus being required to set priorities, I get that. I'm okay with that.

But that last part about disabling mouse integration being a "VERY unusual setup" is pure rubbish, and a total cop-out. Talk about a hand-waving argument. How would you even know what percentage of VirtualBox users know about disabling mouse pointer integration? That's nothing but pure speculation, being used to casually dismiss and marginalize anybody who actually cares about having mouse capture work correctly on dual monitor setups. As if having a dual monitor setup and wanting to run some flavor of Linux as a guest OS on your second monitor is some sort of unheard-of exotic configuration, when in reality that's fairly vanilla. You should have just stopped at "Sorry, there are lots of bugs and the devs have to prioritize."

Last edited 9 months ago by Joe E. S. (previous) (diff)
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use