Navigate to source

The graph gives you the route. Source gives you every punctuation mark. Good investigation moves between them without losing the method you were following.

The problem

You open Door.Enter and see three early returns. One condition looks suspicious, so you want the exact C# line. After checking it, you need to return to the graph and continue the path you were tracing.

When to reach for it

Jump to source when a node tooltip is not enough, when you need surrounding declarations, or when an unsupported shape appears as a placeholder node. Use history when an investigation crosses several methods. Use Reload when the active file changed and you want to run the parse and render pipeline again now.

See it

The active method title in the top rail carries the tooltip Double-click to open source. Method rows open source on a double-click, accessor rows also offer View in Source, and nodes with a recorded source span offer Go to Source.

Do it

1. Find Door.Enter in the Explorer and double-click its row. The editor opens the declaration at its recorded line. An accessor row offers the same jump as View in Source in its context menu.

2. Return to Round Trip Graphs and double-click the active method title. This is the fastest route when the graph is already open.

3. Click the source icon in the top rail, whose tooltip reads Open the active class source., to open the active class source. Use this when you want the file and its neighboring members instead of one selected card.

4. Open a second method from the rail, then a third. Use the back and forward buttons in the top rail to walk the session’s method navigation history.

5. Change the active C# file with your editor and save it. Return to Round Trip and click the Reload icon, whose tooltip reads Re-run the Round Trip parse, adapter, and render pipeline for the active method. It re-runs parsing, adaptation, and rendering for the active method.

6. Right-click a node and choose Go to Source. The jump uses that node’s source span instead of the class start. The item is disabled on a node with no source span, such as one you placed and have not compiled yet.

You should see

You can verify a node against C#, return through the methods you visited, and refresh the graph after an external edit without finding the class again.

Change one thing

Open EnemyPatrol.FixedUpdate, then EnemyStateMachine.ApplyState, then Door.Enter. Walk back twice and forward once. The active graph should follow the history instead of creating another branch in it.

What it reads

For Door.Enter, source navigation lands on an ordinary declaration such as:

C#

public void Enter(PlayerController player)
{
    if (player == null)
    {
        return;
    }
}

Navigation and Reload do not write source. Reload discards no committed C#; it reads the file again and rebuilds the graph from it.

When it goes wrong

When it goes wrong

Symptom	Check	Fix
View in Source is unavailable on a group row.	Check whether the row is an overload or accessor header.	Expand the group and choose the concrete method or accessor child.
Reload is disabled.	Look for an active method title in the top rail.	Select a method, then use Reload.
Back does not return to an accessor view.	Accessor rows are not recorded in method navigation history.	Reopen the accessor from its property group in the left rail.

Next

• Nodes, pins, and wires: read the graph you returned to.
• Edits from outside: understand how saved C# returns to the graph.
• When it refuses: handle a placeholder node without guessing.