The View section enables you to customize the XML documents presentation in XMLSpy.
You can turn off the splash screen on program startup to speed up the application. Also, if you have a purchased license (as opposed to, say, a trial license), you will have the option of turning off the program logo, copyright notice, and registration details when printing a document from XMLSpy.
The window title for each document window can contain either the file name only or the full path name.
Text View settings
Click Text View Settings to open the Text View Settings dialog, where you can enable properties of Text View such as indentation, bookmark margins, and auto-highlighting. The Text View Settings dialog can also be accessed via the menu command View | Text View Settings. The dialog is described there.
Grid View settings
Click Grid View Settings to open the Grid View Settings dialog. The following options for Grid View can be set:
The check boxes in the Display section are self-explanatory. Given below are a few notes for clarification.
•If all cells are not expanded on loading, then the root node and all its descendants are collapsed. You will need to expand each node as you go deeper into the document.
•Optimal widths can be switched on automatically (i) when the document is loaded in Grid View, and (ii) when a set of elements is switched between table display and normal Grid View.
•When optimal widths are switched on, the entire width of cells is displayed so as to fit text in a single line. To achieve this, the following could happen: (i) the table could expand to a width greater than that of the main window, resulting in a scrollbar appearing at the bottom of the window; (ii) text in some cells will extend beyond the right border of the cell (or left border, depending on the writing direction); the text overflow will be indicated by a fadeout of the text or an ellipsis (see next point).
•If text is not wrapped and if the text width is greater than the cell's width, The Text overflow option lets you choose whether to indicate the overflow with a fading out of text near the border or with an ellipsis.
•Sibling nodes can be displayed into sibling groups of 100, 1k, or 10k nodes (see screenshot below). This is useful if you want to save display space in files that have a large number of sibling nodes.
The check boxes in the Editing section are self-explanatory. Given below are a few notes for clarification.
•When changing the type of multiple selected cells, you are given the following options about whether to go ahead with the action of the setting: Always, Never, or Ask (for user decision).
•When changing a JSON type from an atomic type to an object or array type, you are given the following options about whether to go ahead with the action of the setting: (i) Ask (whether the value of the atomic type should be retained as the value of an unnamed child key:value pair, or discarded), (ii) Always (retain the value in an unnamed child key:value pair), (iii) Never (retain the value, that is, discard the value).
•The Paste direction option determines whether a selection in the clipboard is pasted above or below the selected cell.
Filters and formulas can be stored in the metadata of XML and JSON documents. Formulas are stored as processing instructions in XML documents and as comments in some types of JSON document. These settings specify how to proceed with the storing of filters and formulas. In the case of formulas, the if possible terminology refers to the fact that formulas can be saved as comments only in JSON5 and JSONC documents—not in all JSON documents.
The following settings are available:
•If the setting to detect tables automatically on loading is selected, then you can select the minimum percentage of filled table cells that qualify tables to be detected as tables. If the number of filled table cells does not exceed this level, then the structure is displayed as a normal grid with the repeating elements listed one below the other.
•You can also choose whether clipboard contents should be stored as tab-separated values (TSV), or as XML/JSON (depending on the document type). This is a very useful feature: If you want to paste a table from the clipboard to another document, this setting enables you to choose whether the copied table is stored as TSV or with markup. (To see the difference, try pasting a table to a text editor after copying the table to the clipboard in each of the formats.)
An XML Schema datatype can be derived from another datatype. For example, a datatype for E-mail elements can be derived from a base datatype of xs:string (for example, by restricting the xs:string datatype to a specific set of characters). If the base datatype is subsequently changed, you can set the following options:
•Preserve content: If the definitions used to define the derived type can be used with the new base type, checking this option will automatically preserve the definitions.
•Confirm on every modification: After changing the base type, a dialog (see screenshot below) will pop up asking whether the old definitions should be preserved and used with the new base type.
XML files based on a StyleVision Power Stylesheet are automatically opened in Authentic View when this option is active.
You can choose to see the browser view in a separate window, enabling side-by-side placement of the edit and browser views.
The browser engine that is used in Authentic View and Browser View is currently Internet Explorer (IE), and IE is therefore the default browser engine for these two views. Alternatively, you can use Microsoft Edge Web View 2 as the engine for Browser View. If Edge is not installed on your machine, go to the WebView2 download page, from where you can install the Evergreen Bootstrapper. This will enable you to use Microsoft Edge WebView2 as the engine for Browser View.
See the topic Browser View for more information.
Save and exit
After making the settings, click OK to finish.