Present mode in vizzy
Present mode shows a file’s diagrams as full-screen slides, one per diagram, in document order. Use it for a design review, a walkthrough, or reading a flow without the rest of the canvas in the way.
Enter present mode
Section titled “Enter present mode”Hover any diagram on the canvas and a small toolbar appears at its top-right corner. The expand icon, Present full screen, opens the deck:
Copy as PNG · Save as PNG… · ⤢ Present full screen
A full-screen window opens, covering the sidebar, and starts on the diagram you launched from. Each diagram in the file becomes one slide, in document order.
Move through the slides
Section titled “Move through the slides”| Key | Action |
|---|---|
→ ↓ Space | Next slide |
← ↑ | Previous slide |
Esc | Exit present mode |
On-screen chevrons and an n / N counter sit at the bottom for clicking through. The ✕ in
the top-right also exits.
Within a slide you can still pinch to zoom, pan with two fingers, and double-click to reset the view. Hint badges still work, so you can hover or click them without leaving present mode.
Smooth animations: keep node ids stable
Section titled “Smooth animations: keep node ids stable”When you step between two slides, vizzy animates the change instead of cutting from one
image to the next. Every node is tracked by its id (the short handle on the left of
id[Label]). A node that appears on both slides keeps its identity and moves from its
old position to its new one. Nodes that exist on only one slide fade in or out.
If the diagrams in a file share ids, presenting them looks like one diagram evolving rather than a set of unrelated pictures. You can build up an architecture box by box, or follow a request deeper into a system, and the shared pieces stay in place while new ones appear.
Two slides in the same file, sharing user, web, and api:
```mermaidflowchart LR user[User] --> web[Web] web --> api[API]```
```mermaidflowchart LR user[User] --> web[Web] web --> api[API] api --> db[(Postgres)] api --> cache[(Redis)]```Stepping from the first to the second, User, Web, and API slide over to make
room as the layout changes, while Postgres and Redis fade in. Rename api to
backend on the second slide and the animation is lost: the old box fades out and a new one
fades in, because vizzy treats them as different nodes.