I was watching the 6 legged pod tut and was wondering if it was practical or realistic to try and archive or preserve the "Rail" and "Scaling Rail" even after removal. An update to geometry could be made without re-creating it.

I suppose after certain operations the info would have to be discarded due to "other operation" factors ( A dialog could then say "this will destroy previous rail data"), but until that time, a ghost follows the object and can be re-animated again for use. (Am I making MoI slow and bloated?)

Any thoughts will encourage or tame my thoughts.

Burr

[EDIT] THis would also be attractive to the "Vertex bunch" as it keeps the models Maliable for some point.[EDIT]

Hi Burr, actually I do have a lot of ideas right along those same lines, I just really have not had enough time yet to fully dig into it.

Keeping input objects kind implicitly archived is going to involve quite a bit of work because it will mean managing potentially a lot of data, and probably will need ways to browse through it, stuff like that.

But yeah there is no doubt that it would definitely be useful.

I hope to be able to dig into this for version 2.0, but think I'm going to wait until some other areas such as object organization tools are nailed down first.

- Michael

Your a busy man! Figuring out how your going to store "streams" and then use "XmlWriters and XmlReaders" to Manage the structure. (I know, It's late over here!)

Thanks.