Closed HeroesGrave closed 9 years ago
Make a binary format that can be used to store 'Changes' to the harddrive. Changes should only stored on the harddrive if they are 'too old', which should be the case after 8-16 changes. When the user 'undos' changes, then we go and load the youngest stored change into the history.
Thats as far as I can think on this for now.
The problem is that some of the history functions store a lot of complex data.
It's going to be a nightmare to implement and I might have to leave it off for 1.0, unless someone else wants to do it.
Anyone else want to take care of this?
Or should I remove the 1.0 milestone from this issue.
Perhaps instead of saving parameters, serialization could be used. I will do some tests...
I just pushed out a few updates, so make sure to pull in the latest dev. ;)
@Gef4K: Have you got anything working? (or at least something to start from)
If not, I'll just let it throw away old changes.
Then we can push out a 1.0 Beta.
No yet, but I don't give up for later ;)
I'm going to de-nominate this for 1.0.
It will still be needed, just not for the first release.
Renominating for 1.0
See #74.
Done.
That was actually really easy to do with the new serialised changes.
@Longor1996
Do you have any idea how to do this?