A person may have several Google accounts, hence several Google Drives. XXE allows to work directly on all these Drives at the same time. For example, copy some files by dragging files found in a first Drive and then dropping them onto a second Drive.
Example: let's suppose Jane has two Google accounts. First account is associated to email address
<firstname.lastname@example.org>. Second account is associated to (more personal) email address
She'll use "
google:/" to refer to the root folder of her default Google Drive, the one associated to email address
<email@example.com>. (Remember how she authorized XXE to access her Google Drive: she first signed in to her
<firstname.lastname@example.org> Google account. See above.)
She'll use "
google://personal/" to refer to the root folder of her other Google Drive. Here, "
personal" is an arbitrary Drive identifier which is entirely Jane's choice.
Of course, the first time Jane will use "
google://personal/", she'll be prompted to authorize XXE to access her "
personal" Drive, just like she was prompted to authorize XXE to access her default Drive. When this will happen, Jane will take great care to sign in to her
<jane.k.doe.@gmail.com> Google account, and not to her
<email@example.com> Google account.
Technically speaking, "
google:/" is an URL having no authority, while "
google://personal/" is an URL having an authority called "
personal". The two slashes ("
//") preceding the name of the authority are absolutely required.
You may want to revoke XXE authorization to access your Google Drive if you find that the "Google® virtual drive plug-in" is not useful. But there are also other, more imperative, reasons to do that.
When the "Browse Files" tool (and also the URL chooser dialog box) constantly shows a blank window (as if your Google Drive were completely empty), when opening a document in XXE constantly fails after displaying the following "
then it's time to revoke XXE authorization to access your Google Drive in order to be able to grant this authorization again, starting from a clean room state.
This is a two-step operation. First step, actually revoke XXE authorization to access your Google Drive:
Start your Web browser and sign in to the Google account associated to the Google Drive accessed by XXE.
Click your photo. This displays a popup window.
Click Accounts" page having a navigation menu at its left.. The Web browser now displays an "
Click "" and then " ".
Click "XMLmind XML Editor" and then click " ".
Second step, inform XXE about what you did:
Select menu item→ .
After the Preferences dialog box is displayed, select "Add-on|Google Drive" in its left pane.
Select the identifier of the Drive for which you want to revoke XXE authorization. Note that "
(My Drive)" is the identifier automatically given to your default Google Drive (see Section 5.1, “Working with several Google Drives”).
Click Preferences dialog box.to close the
It's not possible to download (and hence, open in XXE) files created using Google Docs. Moreover listing the revisions of this kind of files always shows a blank window.
Write locks are implemented by the means of the
description field of a file. Therefore, you must not hand-edit this field in the case of documents edited using XXE.
XXE authorizations to access one or more Google Drives are stored in file
, where directory
on the Mac.
on Windows XP, Vista, 7 and 8.
C:\Documents and Settings\john\Application Data\XMLmind\XMLEditor7\ on Windows XP.
C:\Users\john\AppData\Roaming\XMLmind\XMLEditor7\ on Windows Vista, 7 and 8.
If you cannot see the "
Application Data" directory using Microsoft Windows File Manager, turn on Tools>Folder Options>View>File and Folders>Show hidden files and folders.
If you use XXE on several computers, after authorizing XXE on one computer, you may safely copy
StoredCredentials to the
directory of the other computer. Doing this will avoid you to also authorize XXE to access Google Drive from the other computer.
 Otherwise, "
google:/" and "
google://personal/" would be two different ways to refer to the same Google Drive.
 Google Drive does not natively support file locking. Though there are more elegant ways to implement application-level file locking, we have chosen to “hijack” the
description field for efficiency reasons.