Auto-Saving Data: Triggering Saves Only on Data Changes

[N-thony]

Fixes #9236
@rdstern I hope this fixes what you have suggested in issue #9236. Have a look.

[rdstern]

@N-thony delighted to see the change. But this backing up information - if true shows a problem at the start, with many macking up in the first 2 minutes!
Log for backing up.zip

[rdstern]

@N-thony it is odd now in a different way. It says backup at the start, (at the bottom) when I think it is checking about undo instead. And now you have taken the notification in the log file away it seems? At least it never eregistered any more, and I was deliberately making changes?

[rdstern]

@N-thony I am getting nervous now, on what we are trying to achieve here. And I'm worried we might be regressing as we make a change. Here is the log file I just loaded, which looks really odd still:

I suggest was abandon this for now and return in January where we try for the full change, namely to only backup a data frame, when something has changed there.

I don't want to get into details of which commands change the "data", because almost all the commands/dialogs have an option to change the metadata.

And I start to worry about how the backing up is supposed to work when we are using scripts as well as dialogs.

[N-thony]

@N-thony I am getting nervous now, on what we are trying to achieve here. And I'm worried we might be regressing as we make a change. Here is the log file I just loaded, which looks really odd still:

I suggest was abandon this for now and return in January where we try for the full change, namely to only backup a data frame, when something has changed there.

I don't want to get into details of which commands change the "data", because almost all the commands/dialogs have an option to change the metadata.

And I start to worry about how the backing up is supposed to work when we are using scripts as well as dialogs.

@rdstern, this is exactly what I was suggestion on Skype.