Changes and history
Use the Changes button to see which classes changed, right-click a method row to copy or delete it, and use back, forward, undo, and redo without mixing them up.
On this page
You open a class, follow one of its methods, then jump to another class it calls. In the Platformer sample, that path might run from the CollectCoin method on PlayerController to ScoreCounter. A few minutes later you want the method you started from, and you also want to know which classes changed on disk. The window keeps those as two separate histories, each with its own buttons.
What it does
Section titled “What it does”Three kinds of history live in the top rail, and each set of buttons touches only its own:
- The Changes button shows which classes differ from version control.
- The back and forward arrows move between methods you have opened.
- The undo and redo arrows step through edits on the canvas of the method you have open.
Keeping them apart means a back click never undoes your work, and an undo click never takes you to another method.
When to use it
Section titled “When to use it”Open Changes before you hand work to a teammate or commit it, to see every class you touched. Use back and forward while you follow calls from class to class. Use undo and redo while you place, wire, and arrange nodes in one method.
What it looks like
Section titled “What it looks like”The Changes button sits in the right half of the top rail, after Auto layout. Its tooltip reads Show modified classes. when Round Trip finds a version-control workspace, and No version control detected. when it does not, in which case the button is disabled. It recognizes Git, Diversion, Plastic SCM, and Perforce workspaces.
Clicking it opens a list grouped under MODIFIED, ADDED, RENAMED, and DELETED. Each row shows a class name with a colored dot and a badge counting its changed methods out of its total, such as 2 / 9. When nothing has changed, the list reads Working tree clean: no uncommitted changes.
Right-clicking a method row in the left rail’s Methods list offers Copy Method Name and Copy Method Full Path, then Delete Method below them. Round Trip does not diff, stage, or revert a file from this menu: open your own Git, Diversion, Plastic SCM, or Perforce client for that. Delete Method is grayed out only on a row for a method already gone from the file, with the reason deleted from the file.
How to use it
Section titled “How to use it”Check what changed, then move through your history
Open the window
Open Tools > Round Trip > Graph view in a project that sits inside a version-controlled folder.
Open Changes
Click Changes. The list opens under the button with your changed classes grouped under MODIFIED, ADDED, and RENAMED.
Pick the changed class
Click a class row. That class opens in the window.
Right-click a method
Right-click one of its method rows. A menu opens with Copy Method Name and Copy Method Full Path, then Delete Method below them.
Go back, then forward
Click a different method row, then press the back arrow beside Compile. The window returns to the previous method. Press forward to go to the later one again.
Undo a move
Drag a node a little way across the canvas, then press the undo arrow in the top rail. The node jumps back and you stay in the same method. Hover undo first: its tooltip names the action it will undo.
5 stepsFull size ↗
What it writes
Section titled “What it writes”Back and forward write nothing. Undo and redo replay the open method’s canvas edits before Compile. Delete Method removes the method from its file immediately; Round Trip does not stage or revert a file for you.
None of these is a substitute for committing. Undo history lasts only until Compile or until you leave the method, and only your own version control client restores a reverted file. Commit before you edit; Protect your game files helps you choose a version control.
When it goes wrong
Section titled “When it goes wrong”When it goes wrong
| Symptom | Check | Fix |
|---|---|---|
| The Changes button is grayed out. | Hover it. The tooltip reads No version control detected. | Open the Unity project from inside the real checkout, with its version-control folder present. |
| Delete Method is grayed out on a method row. | Hover it. The tooltip reads deleted from the file. | The method is already gone from the class; there is nothing left on that row to delete. |
| Undo is grayed out after opening another method or pressing Compile. | Undo history belongs to one method and clears when you leave it or when Compile saves it. | Go back to the method and make the edit again. To change what Compile saved, edit the canvas again and press Compile, or restore the file from your last commit. |
| Forward is grayed out after opening a method from an older point. | Opening a new method from an earlier entry starts a new path and drops the old forward steps. | Carry on from the new path, or open the earlier method again from the left rail. |




