8 Jan
2010
8 Jan
'10
1:07 p.m.
<snip> if that is acceptable to your use case and other use cases you can think of
I'll at it to the "future development" page. I don't think it's an essential part of such a library and necessary for the initial version of it.
This is acceptable to my use case.
but you seem to be experienced in implementing undo/redo so you're welcome to draft a public interface for this. the implementation would be pretty easy I think. the information that describes the changes made by a transaction is already available while a transaction is running.
I'll look into it. Thanks for your time Peder