Changeset 105300 in vbox for trunk/doc/manual/en_US/dita/topics/keyb_mouse_normal.dita
- Timestamp:
- Jul 12, 2024 11:53:09 AM (7 months ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/dita/topics/keyb_mouse_normal.dita
r105289 r105300 38 38 <ul> 39 39 <li> 40 <p> 41 Your <b outputclass="bold">keyboard</b> is owned by 42 the VM if the VM window on your host desktop has the 43 keyboard focus. If you have many windows open in your guest 44 OS, the window that has the focus in your VM is used. This 45 means that if you want to enter text within your VM, click 46 on the title bar of your VM window first. 47 </p> 48 <p> 49 To release keyboard ownership, press the Host key. As 50 explained above, this is typically the right Ctrl key. 51 </p> 52 <p> 53 Note that while the VM owns the keyboard, some key 54 sequences, such as Alt+Tab, will no longer be seen by the 55 host, but will go to the guest instead. After you press the 56 Host key to reenable the host keyboard, all key presses will 57 go through the host again, so that sequences such as Alt+Tab 58 will no longer reach the guest. For technical reasons it may 59 not be possible for the VM to get all keyboard input even 60 when it does own the keyboard. Examples of this are the 61 Ctrl+Alt+Del sequence on Windows hosts or single keys 62 grabbed by other applications on X11 hosts such as the GNOME 63 desktop Locate Pointer feature. 64 </p> 40 <p>Your <b outputclass="bold">keyboard</b> is owned by the VM if the VM window on your host desktop has the 41 keyboard focus. If you have many windows open in your guest OS, the window that has the focus in your VM is 42 used. This means that if you want to enter text within your VM, click the title bar of your VM window first. </p> 43 <p>To release keyboard ownership, press the Host key. As explained above, this is typically the right Ctrl key. </p> 44 <p>Note that while the VM owns the keyboard, some key sequences, such as Alt+Tab, will no longer be seen by the 45 host, but will go to the guest instead. After you press the Host key to reenable the host keyboard, all key 46 presses will go through the host again, so that sequences such as Alt+Tab will no longer reach the guest. For 47 technical reasons it may not be possible for the VM to get all keyboard input even when it does own the 48 keyboard. Examples of this are the Ctrl+Alt+Del sequence on Windows hosts or single keys grabbed by other 49 applications on X11 hosts such as the GNOME desktop Locate Pointer feature. </p> 65 50 </li> 66 51 <li> 67 <p> 68 Your <b outputclass="bold">mouse</b> is owned by the 69 VM only after you have clicked in the VM window. The host 70 mouse pointer will disappear, and your mouse will drive the 71 guest's pointer instead of your normal mouse pointer. 72 </p> 73 <p> 74 Note that mouse ownership is independent of that of the 75 keyboard. Even after you have clicked on a titlebar to be 76 able to enter text into the VM window, your mouse is not 77 necessarily owned by the VM yet. 78 </p> 79 <p> 80 To release ownership of your mouse by the VM, press the Host 81 key. 82 </p> 52 <p>Your <b outputclass="bold">mouse</b> is owned by the VM only after you have clicked in the VM window. The 53 host mouse pointer will disappear, and your mouse will drive the guest's pointer instead of your normal mouse 54 pointer. </p> 55 <p>Note that mouse ownership is independent of that of the keyboard. Even after you have clicked on a titlebar 56 to be able to enter text into the VM window, your mouse is not necessarily owned by the VM yet. </p> 57 <p>To release ownership of your mouse by the VM, press the Host key. </p> 83 58 </li> 84 59 </ul> 85 <p> 86 As this behavior is inconvenient, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides a set 87 of tools and device drivers for guest systems called the 88 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions. These tools make VM keyboard and 89 mouse operations much more seamless. Most importantly, the Guest 90 Additions suppress the second "guest" mouse pointer and make 91 your host mouse pointer work directly in the guest. See 92 <xref href="guestadditions.dita#guestadditions"/>. 93 </p> 60 <p>As this behavior is inconvenient, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides a set of tools 61 and device drivers for guest systems called the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest 62 Additions. These tools make VM keyboard and mouse operations much more seamless. Most importantly, the Guest 63 Additions suppress the second "guest" mouse pointer and make your host mouse pointer work directly in the guest. 64 See <xref href="guestadditions.dita#guestadditions"/>. </p> 94 65 </body> 95 66
Note:
See TracChangeset
for help on using the changeset viewer.
