An object becomes an entrance
Any suitable element can own one child canvas.
We do not promise depth.
We let you check it in action.
Pick a scenario. One click selects an element, a double click opens the child canvas that belongs to it. For the keyboard and for touch screens, the “Open the child canvas” button stays alongside.
How it worksFrom an element to a level of its own
A double click leads into the child canvas.
Right now: “API Gateway” is selected — its child canvas can be opened.
Child canvasInside — 4 elements.Double-click the element to open the level.
One click selects an element. A double click opens its child canvas.
The path stays visible in the breadcrumb trailAn element owns a canvas of its ownA level keeps its own camera and contents
Verified in the app · Native e2e
Look at the real states, step by step.
The shots come from an isolated Russian-language profile of the current Schemas build, so the interface in them is Russian. Click any shot to look at the detail.
01 / Local library
4 canvases in the local libraryA project starts with a whole context
Root canvases are gathered in one library: the diagram, its branches and its material do not scatter across separate windows and services.
Scenario · Windows files
Explorer → project → Explorer
This is what the working cycle looks like — the one worth showing in a demo.
01Drag or paste
An Explorer drop and CF_HDROP both go through one import flow.
02Find your way in the card
The preview and the original are available next to the diagram, with the name and MIME type intact.
03Hand it back to Windows
“Open in Explorer” and “Save a copy…” return the material to the outside.
What actually happens
One project. Several independent levels.
The parent element stays where it is. Its child canvas keeps its own contents and camera, and the breadcrumb trail keeps the path back to the root.
A level lives on its own
Its own zoom, camera position, elements, links and action history.
The path is never lost
The breadcrumb trail leads to any ancestor, and search opens the exact level.
The project stays whole
The tree is saved in the local library and travels in a .cppboard file.
Project → root canvas → element → child canvasA recursive ownership model
Search brings you back into contextNot just the file — the exact element in the tree
Compare the approaches