Closed HeroesGrave closed 10 years ago
That is a VERY good Idea! Don't forget to think about on the 'save history on harddrive to make it infinite'-thing.
Be aware that you need to add the layer-path to the history entries, so reverting a change affects the correct layer while reverting things!
I did a very lazy solution that simply wraps the current system.
It listens to all the changes happening, and stores a reference to them along with the canvas involved. When reverting/repeating changes it just pops one off the stack, calls revert/repeat on that canvas, and pushes it onto the other stack.
To avoid everything being a mess, I've decided to scrap the idea of one history per layer.
It will just end up being to confusing anyway.