Custom Query (16363 matches)
Results (2104 - 2106 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9321 | duplicate | PutMouseEventAbsolute function produces a click with -2 offset on each coordinate -> duplicate of #7566 | ||
| Description |
I am using VirtualBox SDK to move/click mouse on guest from app running on host through IMouse interface. I've noticed that when I call PutMouseEventAbsolute(x, y, 0, 0, 1) the real click happens at (x-2,y-2) position. GA are installed, but Mouse Integration is disabled for the guest. I have created .NET wrapper for VirtualBox.exe with tlbimp tool. My program looks like this: / VirtualBoxClass vbc = new VirtualBoxClass(); IMachine vm = vbc.FindMachine("w7"); SessionClass s = new SessionClass(); vm.LockMachine(s, LockType.LockType_Shared); s.Console.Mouse.PutMouseEventAbsolute(100, 100, 0, 0, 1); / the click happens at (98,98) |
|||
| #9449 | wontfix | Cursor is invisible when using PutMouseEventAbsolute method | ||
| Description |
I am using VirtualBox SDK to move/click mouse on guest from app running on host through IMouse interface. Mouse is moved successfully and clicks can be emulated, but the cursor becomes invisible on the Guest just after PutMouseEventAbsolute method is called. Once I touch my real mouse - the cursor appears at "correct" position (the position at which it has been moved by PutMouseEventAbsolute method call). GA are installed, but Mouse Integration is disabled for the Guest. |
|||
| #8396 | fixed | Virtualbox crashes with general protection fault and sort-of kills X | ||
| Description |
Using an Ubuntu Maverick install with the latest kernel from Ubuntu natty (unstable), Virtualbox crashes when starting a VM and messes up the X session (reboot required). The Kernel I used was the Ubuntu image linux-image-2.6.38-4-generic from natty, system architecture is amd64. After the crash (see Kernel log buffer) I can see the Kernel log buffer, still use the X mouse cursor, however, when killing the X session (SysRq SAK) a lot of processes remain in state D (uninterruptible sleep) and a reboot is required. |
|||

