Now, the obvious response question, Dale, is this: Why? What program, in the right minds of any programmers, needs to store a complete scene/document/data set for every change in order to perform an undo? No person without a Python script doing so could possibly change that much information in a scene in one click. Even loading a fully morph-injected V3 wearing twenty layers of clothing figures and magnets with props should only produce a small data set that says: "CR2 so and so was loaded" in an undo stack. So it sounds like the core structuring of Poser is completely horrid and uncondusive to undos. Restructure (as was promised in 5). Restructure. Restructure. Restructure. When code sucks, change it.

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