Qualien, yes, I see that there are actually two issues concerning undos which depend on the undo type. As someone mentioned, dial twiddling costs one real value (4 bytes of memory). You should be able to store thousands of undos for anything that can be encapsulated as a dial change (whether in the Parameters window or via direct manipulation). I think that this form of multiple undo would satisfy most of us for some time. 4-bytes * 10,000 undos = 40,000 bytes (40KB). That is practically throw away storage. You could do this, literally, on the Program Stack! Of course, some reference (what changed on what) will be needed. But that could be done simply as [internalName][figureNumber][channel][real value]. At worst, that might incur, let's say 1024 bytes. So divide 10,000 undos by 1024. You still have room for ~10 undos. In 40KB of memory! But for some reason, the programmers at CL can't even do this! I would sell the code and go into flower arranging if it's THAT bad... :)

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone