3.2. Node Path bar

The node path bar displays the path of

The path of a node is

preceded by the path of its parent element.

The node path bar is a very convenient tool for selecting nodes, duplicating and deleting elements:

User interaction in the node path barCommand
Click on node name.Selects this node.
Ctrl-click on element name.Selects this element and then creates a new element of same type (if the grammar constraining the document allows to do so) after this element.
Shift-click on element name.Selects this element and then creates a new element of same type (if the grammar constraining the document allows to do so) before this element.
Click on element name with right mouse button.

Displays a popup menu with the following items:

Insert Same Element After

Same as command triggered by Ctrl-click on element name.

Insert Same Element Before

Same as command triggered by Shift-click on element name.

Delete

Selects the node clicked upon and then deletes it (if the grammar constraining the document allows to do so).

Copy XPath

Selects the node clicked upon and then copies its XPath (example: /section[1]/para[1]/text()[1]) to the clipboard.

Drag the icon which looks like a bookmark

Drag and drop in another application, the location of the document being edited in XXE.[a]

Do not forget to save the document being edited in XXE before dropping its location in a viewer application.

[a] Linux users: Java™ 1.4 only supports the Motif drag and drop protocol. Therefore if you use an ancient Java™ runtime, drag and drop will not work between XXE and your favorite Gnome or KDE application.

3.2.1. Non-editable nodes

The path of a non-editable node is displayed using a dimmed color. A non-editable node has been pasted in the document being edited after using command Copy as Reference.

In order to modify such node, one must edit the document containing it in a separate window. A convenient way to do this is to use the buttons which are at the left of the node path bar.

3.2.2. Elements which are in non-validating mode

Normally, XMLmind XML Editor works in validating mode. In such mode, the author can only do the editing operations which are allowed by the DTD or schema. For example, the author cannot remove required attributes (unless he/she uses Force Removal).

When an element is found to be invalid, XMLmind XML Editor automatically switches to a lenient editing mode for this element and all its descendants.

After the invalid element is fixed by the author, XMLmind XML Editor automatically switches back to its normal, validating, mode.

  • An element underlined in orange means that this element is in non-validating mode 1. In this mode, XMLmind XML Editor still suggests the right attributes and child elements to the author. But these are only suggestions: the author may add and remove any attributes and child elements he/she wants, and this, at any place and in any number.

  • An element underlined in red means that this element is in non-validating mode 2. In this mode, XMLmind XML Editor is not able to suggest the right attributes and the right child elements to the author. The author may add and remove any attributes and child elements he/she wants, at any place and in any number.

Note that, in the case of certain RELAX NG schemas, XMLmind XML Editor may automatically switch to a lenient editing mode, even if the underlined element is perfectly valid. This behavior is explained in great details in XMLmind XML Editor - Support of RELAX NG Schemas.