![]() ![]() ![]() displaying menus, as it seems to me the earliest you can send it is at the time when you can send the "correct" keyup event. In particular, I don't see how you can send the "spurious" Alt keyup event "early" enough to prevent Windows from e.g. If the code is correct, it sounds like it is designed to deal with some other situation. When I press Tab, that combination is trapped by the host, so will never reach the guest anyway. I am unsure what the benefit of the extra key up event is: if I hold down Alt and wait for 1s before pressing Tab, then of course the guest should receive Alt keydown, and the Windows menus should activate. Non-modifier is pressed, and key combination is trapped by host OS VirtualBox detects this situation, and sends a key up event to the guest.Modifier is pressed with guest OS focussed, key down event is generated.It would seem that what is needed is something like this: Just thinking about the particular problem here, I am unsure why it is quite so complicated. if I hold down Alt for < 0.5s, I often don't get the problem) suggest any other lines of thought? Does the fact that timing seems to be important (i.e. ![]() I also cannot see why sending two key up events should be a problem, unless there is a bug in Word. I am using a UK keyboard, so that code only run for Brazilian keyboards should not be a problem for me. Perhaps you could post here (or even add to the VirtualBox documentation) a link to the Windows 7 version of keylook, as it sounds useful for debugging other key problems. Thanks very much for continuing to investigate this problem. I'm reporting this here instead of as a separate bug as I think it's just another symptom of the same problem.įor now I've changed my host key to the Scroll Lock button, that appears to be a useful workaround for now. A couple of times now that has wound up locking the mouse and keyboard within VirtualBox when I come back to it, and it appears to coincide with times the control key has gotten stuck down. I also run the VMware Infrastructure Client within this virtual machine, and that requires the use of Ctrl+Alt to free the mouse from its client windows. Tapping the left control key on the keyboard does seem to free it up again. It means typing is impossible, and unlocking a machine with your password is a nuisance until you spot what is going on. I'm running VirtualBox full screen on my second monitor, and often hit ctrl so that I can leave the virtual machine running, but free the mouse so I can continue working on my primary screen.Īfter doing this, about a quarter of the time, I go back to the guest to find the control key stuck down. Does VirtualBox always send the "key-up" message to the guest after the host key has been pressed? Not all the time, but regularly enough to be a nuisance, the host key gets stuck down within the guest after it's been used to free up the mouse. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |