Say you start on Project 1, let’s say you have performed a “Save” command at some point on this Project 1 and since then you have made changes.
Now you perform a “Save as new”. Project 1’s active autosaved state is now “synced to card” which is the manuals way of saying its autosaved active state is now fully saved to the CF card.
Renaming as Project 2 with the “save to new” command you now have an identical copy of Project 1’s active state now in the form of Project 2’s active state and Project 2 is now active. Project 2 does not have a saved state at this moment, only an active state. If you start making changes on Project 2 there is no way within the project itself to revert back to the exact state it was in when you saved as new.
If instead you were to perform “save” project on Project 2 immediately after you performed the “save as new”, you then create a saved state for Project 2 that allows you to then modify the project thus changing the active state and then by performing a “reload project” it will load the saved state of Project 2 that you created and it will be exactly as it was when you saved to new.
If you then change project back to Project 1 it will load the “synced to card” active state it was left in, the same state that was “saved to new”. Since there was a “save” command performed on Project 1 at some point you have the option to revert to that by performing a “reload project” command. If you now “reload” project Project 1’s active state is now identical to the saved state until you make you first change which then modifies the active state version…
Phew… This makes perfect sense to me but it’s still confusing as all get out…