8 — Reference

This chapter tells no story: it recapitulates. Every shortcut, every button, every menu and every gesture in Debug XML Tool, in tables, with the condition that makes each available and the chapter that explains it.

Worth keeping open beside the application while you find your feet.

---

8.1 Keyboard shortcuts

Global

Active wherever the focus happens to be.

The three font shortcuts work equally well with the numeric keypad.

In the editor

Active when the cursor is in the code.

---

8.2 The toolbar

In their real order of appearance. Every button is icon-only: hover to read the label given below.

At the far right: the state badge (IDLE / RUNNING / PAUSED) and the status message.

The menu of the schema button

---

8.3 When the debugging commands are active

Whether the buttons are enabled tells you on its own where execution stands.

---

8.4 The explorer context menu

Right-click in the left-hand panel. The menu adapts to what you pointed at.

Deletion asks for confirmation — « Permanently delete "…"? This action cannot be undone. » — and really does act on the disk.

---

8.5 The editor context menu

Right-click in the code.

To these are added the standard editor entries: cut, copy, paste, format, command palette.

---

8.6 Mouse gestures

The navigation gesture is not the same everywhere, and that is not an oversight: the search and diagnostic panels navigate on a single click, like a classic "search in files", because there you run through a list of results. The inspection panels ask for a double-click, because there you first select in order to read.

---

8.7 The Settings menu

Changing theme and language is immediate, with no restart.

---

8.8 The bottom panel tabs

Thirteen tabs, icon-only. Each can be detached to the right by right-clicking its header, and reattached to the bottom the same way — only one detached at a time.

An empty panel always says what will fill it — Run the profiler (⏱) to analyze performance., Right-click a folder in the explorer to validate it, No variables — the debugger is not paused.

---

8.9 Where things are displayed

Three areas receive messages, and the distinction is constant:

If a run produces nothing, look at the status message before the console: that is where configuration errors go.

An error coming from another file — a broken associated schema, a faulty xsl:include module — does not soil your document: it goes to the console, prefixed [Validation] External diagnostic.

---

8.10 The most frequent status messages

---

8.11 File types

Neither JSON, nor XQuery, nor graphical Author/WYSIWYG editing.

---

8.12 Limits, a recapitulation

Gathered here for reference; each is explained in its own place.

Engine

• Transformation by Saxon-HE: no schema-aware transformation, no streaming.
• XSD validation follows the W3C XML Schema 1.0 standard.

Debugging and analysis

• The "go to source" highlight applies to the whole line, not to a range of columns.
• Template coverage is relative to the input document: a template not triggered on this XML is not absolute dead code, and a template inlined by the optimiser may appear untriggered.
• Back-mapping is unavailable on PDF export.

Navigation and refactoring

• Symbol navigation and renaming: .xsl / .xslt tabs only, and never match templates — resolving them is the debugger's business.
• Rename and replace are only undoable in open tabs.
• The search ignores files larger than 2 MB and truncates beyond 5,000 results.

Validation and comparison

• Batch validation reflects the disk, ignores files larger than 2 MB, caps at 10,000 problems, and validates xsl:include modules in isolation (false positives possible).
• The comparison treats element order as significant, falls back to text mode beyond 10 MB, caps at 5,000 differences, and does neither folder diff nor merge.
• Catalogues only resolve towards local files.
• An XSpec scenario cannot yet be debugged step by step.

---

8.13 What the application remembers

From one session to the next, without asking you anything:

Two different workspaces therefore have their own scenarios, their own watches and their own catalogues — without interference.

---

What next

You have been all the way round. To come back to a point:

• Getting started — from an empty folder to a first breakpoint.
• The interface — the five areas of the window.
• Editing — completion, formatting, validation as you type.
• Transforming & exporting — formats, parameters, scenarios.
• Debugging — breakpoints, stepping, inspection.
• Analysing — profiler, coverage, back-mapping.
• Navigating & refactoring — definitions, references, renaming.
• Validating & comparing — batch, catalogues, comparison, XSpec.