Everything that happens to a profile is logged for autosave purposes, and those same events can be used to implement undo/redo functionality for the profile. This may not be necessary given the simplicity of tasks being performed in the UI, but then again, why not?
A more advanced version of this is to support either large-scale rollbacks or individual record rollbacks from the profile history (#4). That could be a lot more useful, for example if someone accidentally loaded an old/bad profile, used a Reset function and didn't like the result, etc.
It's easy to underestimate the number of scenarios leading to "I can't remember what I did, and now things are broken" - they're hard to predict but happen often in practice, so let's have a safety valve.
Everything that happens to a profile is logged for autosave purposes, and those same events can be used to implement undo/redo functionality for the profile. This may not be necessary given the simplicity of tasks being performed in the UI, but then again, why not?
A more advanced version of this is to support either large-scale rollbacks or individual record rollbacks from the profile history (#4). That could be a lot more useful, for example if someone accidentally loaded an old/bad profile, used a Reset function and didn't like the result, etc.
It's easy to underestimate the number of scenarios leading to "I can't remember what I did, and now things are broken" - they're hard to predict but happen often in practice, so let's have a safety valve.