Opened 10 years ago
Last modified 6 years ago
#14053 new enhancement
separate caps-lock state between host & guest
Reported by: | RandomName123 | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.3.26 |
Keywords: | capslock unlinked | Cc: | |
Guest type: | all | Host type: | all |
Description
I'd like to suggest that each VM settings page have an additional setting for linking and unlinking the caps-lock state from the host to the guest (might as well include num-lock and scroll-lock states too).
The setting could be: [linked to host] or [unlinked to host]. Unlinked would permit completely different states between the host and guest. But the default would be [linked to host].
I'm thinking that having it as an automatic switch (like with mouse cursor capture and release) would be easiest for the user. Each VM would have to keep track of its own caps-lock state. When the user returns to that VM, caps-lock is in the same state as when they left it.
A minor convenience? Yes.
More trouble than it's worth? Quite possibly.
Thanks for reading.
:)
Change History (3)
comment:1 by , 7 years ago
comment:2 by , 6 years ago
Related discussion in the forums: https://forums.virtualbox.org/viewtopic.php?f=9&t=67339
comment:3 by , 6 years ago
Read the VirtualBox manual, chapter 9.27 Support for Keyboard Indicator Synchronization The only inconvenience of having this feature enabled is that it's still buggy (e.g. having a Windows host with NumLock enabled by default and having a Linux guest with NumLock disabled by default, it sometimes gets confused and the host NumLock becomes disabled, when returning to the host).
+1 from a user with Windows host with Linux guest for development. I find myself memorizing the current caps lock state and failing at it. Other times I am suprised by laptop/keyboard caps lock led blinking on and off when switching between host and guest.