NodemancyDocsMapLibraryCards
Troubleshooting

Clicking a lens opens a tray instead of the lens

Nothing is lost. The lens became a container when you nested something under it, and a container that holds no nodes of its own has no graph to draw.

What happened

A lens becomes a macro lens the moment another lens names it as its parent. You never set that — it is derived from the arrangement, so it cannot fall out of step with reality. Remove the last child and it is an ordinary lens again.

A macro lens's chip in the switcher toggles its tray — the lenses inside — rather than becoming the active lens. Arrow-stepping through lenses skips it. So from outside, the lens you clicked appears to have been replaced by a drawer.

Your nodes are exactly where they were. Nothing about nesting moves, hides or deletes content — it changes one thing, which is what that chip does when clicked.

The rule, precisely

A lens that…Its chip
has no childrenSelects the lens. The ordinary case.
has children and no nodes of its ownOpens the tray only. There is genuinely nothing to draw — selecting it would strand you on an empty graph.
has children and nodes of its ownDoes both: opens the tray and selects the lens.

That third row is the important one, and it is newer than some of the language around it. If you have parented an empty lens under a lens with three hundred nodes, those nodes are still one click away — the chip opens the tray and the lens together.

Getting back to the nodes

  • Look in the tray.The children are listed there and each is selectable normally. If you nested Chemistry under Science, Chemistry is inside Science's tray.
  • Use the Library. It lists entries without going through the lens switcher at all, so it is the fastest way to confirm nothing is missing.
  • Undo the nesting. Move the child back out and the parent stops being a macro lens the moment it has no children left.

Editing a macro lens

Its settings live in the tray, not on the main gear — because a macro lens is never the active lens, so a control keyed to the active lens could never reach it. Open the tray, and the wing's own settings are there.

Two related surprises

Nesting stops at one level. A macro lens holds lenses; those lenses hold nodes. You cannot put a macro lens inside a macro lens, and the app refuses rather than quietly accepting it.

An empty wing can be filled. A wing with no members is not a macro lens — macro-ness is derived — so it has no tray, and the tray used to be the only route to the panel that assigns members. It is not any more: the members panel opens on an ordinary lens too, so a wing created by mistake is not stuck being one.

Why not just make every macro lens selectable

Because there is nothing to show. A container with no nodes of its own would open onto blank canvas, and a blank graph is indistinguishable from a broken one — you would be trading a surprising tray for a screen that looks like data loss.

The version that would work is a macro overview: the union graph of everything in the wing's member lenses. That is designed and not built. When it lands, macro chips become selectable and this whole page becomes a note about how things used to be.

Related