Changes and history

You open PlayerController, follow CollectCoin, then jump to ScoreCounter. A few minutes later you want the method you started from, and you also want to know which classes changed on disk. Those are two histories with two different jobs.

The problem

Source-control state, visited methods, and reversible canvas edits can all look like “history.” Treating them as one stack would make a Back click undo work or an Undo click navigate away.

Round Trip keeps them separate: Changes for source files, back and forward for places, undo and redo for graph edits.

When to reach for it

Use Changes before reviewing or handing off source work. Use back and forward while tracing calls across classes. Use undo and redo while shaping the current method’s draft or layout.

See it

The Changes icon in the top rail, whose tooltip reads “Show modified classes.”, is enabled only when Round Trip detects a supported version-control workspace. If none is detected, its tooltip reads “No version control detected.”

Opening it shows the modified class list. File markers distinguish modified, added, renamed, and deleted source. The detector reads the active provider’s status, including Git, Diversion, Plastic SCM, and Perforce workspaces.

Method rows in a Git checkout expose three source actions:

Action	What it actually does
Diff against HEAD	Runs a file diff against HEAD, then writes the output to the Unity Console. The menu starts from a method row, but the diff covers its source file.
Stage / Unstage	Stages the backing file when unstaged, or removes that file from the staged set when already staged.
Revert Method	Shows a confirmation, then restores the entire backing file to HEAD. Other edits in that file are lost too.

Do it

1. Open Tools > Round Trip > Graph View inside a version-controlled project.
2. Click the Changes icon and choose a modified class.
3. Right-click one of its method rows.
4. Choose Diff against HEAD and read the file diff in the Unity Console.
5. Use Stage / Unstage only when the whole file is ready for that state.
6. Use Revert Method only after reading the confirmation that the entire file will be restored.
7. Open another method, then use back and forward to move through visited methods.
8. Move a node or make another reversible graph edit, then use undo and redo without leaving the active method.

You should see

Back and forward restore method navigation. They keep a session-only history and never apply source edits. Undo and redo describe the next graph action in their tooltips, and their history clears when you switch methods so an edit cannot leak into another graph. A Compile that writes the method’s graph edits also clears it, because that work now lives in source.

Change one thing

Open PlayerController.CollectCoin, then ScoreCounter.OnCoinCountChanged. Press back once. You return to CollectCoin. Move one node and press undo. The node returns to its prior position, but you stay in CollectCoin.

What it writes

Navigation writes no source. Undo and redo replay the current method’s in-session graph actions. Stage / Unstage changes the version-control index for the whole backing file. Revert Method replaces that whole file with its HEAD version after confirmation.

When it goes wrong

When it goes wrong

Symptom	Check	Fix
Changes is disabled.	Read its tooltip and confirm the project sits inside a detected workspace.	Open the Unity project from the real checkout, with its provider metadata available.
Diff against HEAD reports no output.	Check whether the backing file already matches HEAD.	Choose a method in a changed file or refresh the provider state.
Revert Method would remove unrelated work.	Read the path in the confirmation dialog.	Cancel and preserve the other file edits before restoring the file.
Undo is disabled after changing methods or after Compile.	The edit history belongs to one method. It clears on navigation and after a Compile writes the graph.	Return to the method and make the intended edit again. To change what a Compile wrote, edit the graph again and Compile.
Forward is disabled after opening a new path from an older entry.	A new navigation branch discards the old forward branch.	Continue from the new path or reopen the earlier method from the Explorer.

Next

• Preview and Compile
• Navigate to source
• Graph configuration files