Dan, yes! Give the user a little control of the export scaling, please! Especially BVH where our only choices are "Do not scale" or "FUBARFAOA". I thought about the undo issue last night before bed. What is the problem here. Conceptually, moving from a single undo-level to multi-level undos is very simple. IOW, if you can do one undo, supporting more than one undo is the straight forward addition of a stack (one of the most basic programming structures around). This made me consider why they have avoided it for over a decade! The answer might be that the current undo implementation is so amazingly horrid that noone dare touch the code to fix it (in order to properly implement an undo stack). Adding the variety of undos that users would like might not be simple, but extending the number of currently available undos should be able to be done in a week. I take it that they'd need to destroy the codebase in order to do it otherwise. And that bolsters my suspicions. Under these conditions, then, it may be time to get some real programmers who have not so much vested interest to tear this heap of archaic muck into little pieces and reconstruct it. Otherwise, sorrily to say, Poser 99999 will still have that one undo... LOL ... pathetic...

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