1. If it can be done in LW, C4D, Vue, Bryce (!), and a myriad other 3D applications then the argumentation about memory usage is moot - give it up already. I've done multiple undos in C4D with hundreds of thousands of polygons, stage lights (dozens), cameras, complex animations involving XPresso nodes - Poser can't come close to that complexity and it can't do multiple undos?! Quoting the effable P&T: Bullshit!

2. Thank you wolf359 for making my point before I found this post! :)

3. lmckenzie: My vote = C

It has already been stated in another thread that the programmers do not think it can be done. Translated, that means that the codebase is such a noodly, intractable mess that only by completely reworking it could it be made to implement features that have been in every other application for over a decade. :)

KDoug: Animation frames only store value changes in keys - not additions/removals, application of Pose settings, etc. But your point is taken (and I've already made it in another thread).

Message edited on: 05/07/2005 20:28

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