Interesting example (figure deletion) Pantast, although I think it illustrates how non-trivial some simple ideas can be. Poser cannot rely on the original cr2 remaining intact, and during the course of the session, materials could have been customised and any number of morph targets (with new delta sets) could have added, or deleted using the hierarchy editor and deformers. All parameter setting would have saved as well across all animation frames. As a result, in order to provide a deletion undo function Poser would have to perform the equivalent of a single figure/object pz3 save (on memory or disk) every time a deletion was performed. This is not necessarily an impossibility (in fact it may be fairly trivial to implement if the existing "save" code was reused), but it would obviously have added a performance overhead. The counter argument is just to tell users to "save often", so they can control how the overhead affects them. Then again it could always be implemented as a switchable option. Bill