1 | <?xml version='1.0' encoding='UTF-8'?>
|
---|
2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
|
---|
3 | <topic xml:lang="en-us" id="guestadd-dnd">
|
---|
4 | <title>Drag and Drop</title>
|
---|
5 |
|
---|
6 | <body>
|
---|
7 | <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables you to drag and drop content from the host to the
|
---|
8 | guest, and vice versa. For this to work the latest version of the Guest Additions must be installed on the guest. </p>
|
---|
9 | <p>Drag and drop transparently allows copying or opening files, directories, and even certain clipboard formats from
|
---|
10 | one end to the other. For example, from the host to the guest or from the guest to the host. You then can perform
|
---|
11 | drag and drop operations between the host and a VM, as it would be a native drag and drop operation on the host
|
---|
12 | OS. </p>
|
---|
13 | <p>At the moment drag and drop is implemented for Windows-based and X-Windows-based systems, both on the host and
|
---|
14 | guest side. As X-Windows supports many different drag and drop protocols only the most common one, XDND, is
|
---|
15 | supported for now. Applications using other protocols, such as Motif or OffiX, will not be recognized by <ph
|
---|
16 | conkeyref="vbox-conkeyref-phrases/product-name"/>. </p>
|
---|
17 | <p>In the context of using drag and drop, the origin of the data is called the <i>source</i>. That is, where the
|
---|
18 | actual data comes from and is specified. The <i>destination</i> specifies where the data from the source should go
|
---|
19 | to. Transferring data from the source to the destination can be done in various ways, such as copying, moving, or
|
---|
20 | linking. </p>
|
---|
21 | <note>
|
---|
22 | <p>At the moment only copying of data is supported. Moving or linking is not yet implemented. </p>
|
---|
23 | </note>
|
---|
24 | <p>When transferring data from the host to the guest OS, the host in this case is the source, whereas the guest OS
|
---|
25 | is the destination. However, when transferring data from the guest OS to the host, the guest OS this time became
|
---|
26 | the source and the host is the destination. </p>
|
---|
27 | <p>For security reasons drag and drop can be configured at runtime on a per-VM basis either using the <b
|
---|
28 | outputclass="bold">Drag and Drop</b> menu item in the <b outputclass="bold">Devices</b> menu of the virtual
|
---|
29 | machine, or the <userinput>VBoxManage</userinput> command. </p>
|
---|
30 | <p>The following drag and drop modes are available: </p>
|
---|
31 | <ul>
|
---|
32 | <li>
|
---|
33 | <p><b outputclass="bold">Disabled.</b> Disables the drag
|
---|
34 | and drop feature entirely. This is the default when creating a
|
---|
35 | new VM.
|
---|
36 | </p>
|
---|
37 | </li>
|
---|
38 | <li>
|
---|
39 | <p><b outputclass="bold">Host To Guest.</b> Enables drag
|
---|
40 | and drop operations from the host to the guest only.
|
---|
41 | </p>
|
---|
42 | </li>
|
---|
43 | <li>
|
---|
44 | <p><b outputclass="bold">Guest To Host.</b> Enables drag
|
---|
45 | and drop operations from the guest to the host only.
|
---|
46 | </p>
|
---|
47 | </li>
|
---|
48 | <li>
|
---|
49 | <p><b outputclass="bold">Bidirectional.</b> Enables drag
|
---|
50 | and drop operations in both directions: from the host to the
|
---|
51 | guest, and from the guest to the host.
|
---|
52 | </p>
|
---|
53 | </li>
|
---|
54 | </ul>
|
---|
55 | <note>
|
---|
56 | <p>Drag and drop support depends on the frontend being used. At the moment, only the <ph
|
---|
57 | conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> frontend provides this functionality. </p>
|
---|
58 | </note>
|
---|
59 | <p>To use the <userinput>VBoxManage</userinput> command to control the current drag and drop mode, see <xref
|
---|
60 | href="vboxmanage.dita#vboxmanage"/>. The <userinput>modifyvm</userinput> and <userinput>controlvm</userinput>
|
---|
61 | commands enable setting of a VM's current drag and drop mode from the command line. </p>
|
---|
62 | </body>
|
---|
63 | </topic>
|
---|