Unless I’m missing something, Gig Performer has a behavior by which if you have a rackspace open in a gig file, and you make any change, and then move to the next rackspace, those changes are retained in the racksapce you moved away from. You then save the gig file and there’s no real way, short of hoping you exported the rackspace previously, to ‘revert’ to the previous version. You may have made a change by mistake, and there are other unintended consequences.
With my previous host, the default behavior in it’s ‘rackspace’ (called a scene) was that if you moved from one scene to another without intentionally committing any changes, they were lost. There were benefits and drawbacks to this behavior, but I would like it if there was a global setting in GP that unless you intentionally committed changes to a rackspace before performing an action that would move you to another rackspace, you would simply ‘lose’ those changes. I think this might also cut down on GP file ‘bloat’ because I suspect in some cases, people are creating unintentional changes and then subsequently committing them to disk when they save the gig file.