Why do we repeat our backing up in R-Instat if nothing has changed in the log file?

[rdstern]

@ChrisMarsh82 and @N-thony and @Patowhiz I am writing the help and have got as far as the log file. Here is a bit of my latest:

I often have R-Instat open, while I am doing other things. I notice, from the figure above that it backs up every 10 minutes, even if I have not used it, since the last one? Couldn't it check that, and only backup if something has changed? I can imagine situations (with large datasets) where this could be very annoying?

[Patowhiz]

@rdstern I agree.

I'm surprised by that as well, but what surprises me even more is why the back up operations are written on the log file. I think this was not the case in previous versions. I think the back up operations should not be in the 'users' log file. It should be silent and something that a user never needs to be aware of until when the application crushes or user unintentionally kills the application.

[rdstern]

@Patowhiz happy with your support of my first point. The times of backing up have been included recently - and I'm afraid at my request! That's by @N-thony and after discussions with Stephen. They form part of our recent "ultimate undo system" for those who can cope - and I hope you'll like it.
That's also why I was so pleased to have Antoine's new "spreadsheet style" undo system in the latest versions. That's in contrast to the R-user type undo, which uses the information in the log file!
Remember we back-up the data every 10 minutes (by default). Now suppose we have a problem and need to go back a bit.
a) Use Tools > Backup to restore the data up to the last backup.
b) Use the log file, from the date/time of the last backup, as much as you need to complete your data rescue.

Neat eh, for those who can cope?