Hi Burr,

> Can you "know that one is in it" and have some kind
> of "Reference object" import in?

Actually that does happen already - when opening a file that contains objects that MoI does not handle, they are actually stored in an internal table so that if you save back out again those objects can be written to the file instead of just lost. That's to try and enable "round tripping" of data in the 3DM file to help avoid data loss.

But there is no visual representation of them.


> So like the scene browser would have an entry for "Non
> Editable Mesh object" or something with a "point" at it's
> bounds center (as opposed to an "Error")

This would be quite a bit more work to make entries in the scene browser and visual representations of special non-editable objects.

I could certainly do that, but it's the age-old question - what other kinds of actual editing features would you like for me to sacrifice in order to spend time working on special stuff for non-editable "foreign" objects?

It's hard to justify spending much time on an area like this that does not really affect someone who is just modeling inside of MoI.

- Michael

Not really some kind of representation of the object, more like a "label" instead of an "Error". So since the objects exist and are being stored, and it really isnt an "error", just a label in the Scene browser that states "Stored mesh object" or something like that.

Anyway, it was just a thought.

Hi Burr, so normally in the Scene browser you can use the scene browser to select or hide or show things...

Would you expect for those operations to work on these special objects?

What about deleting them? It could be kind of frustrating if things showed up populating the scene browser but you had no way of actually doing the normal kinds of interactions with them.

I think that would likely open up a big can of worms with a lot of work trickling down from it.

- Michael

Got it. Short sightedness gets the best of me.

Hi Burr, well don't get me wrong I think it is a good idea.

It's just one of those ideas that is hard for me to implement because there is probably a fair amount of work involved.

- Michael

Well one thing you can do is perhaps limit the drop down format options depending on what's in the scene.

This way there wouldn't be any polygon export formats in the list if there wasn't any surfaces to mesh.

-Will

Hi Will,


Maybe... But that could just push the question off to a different one - then it would be "why isn't the file type I want in the list?", instead of "why didn't anything get written to the file?"

- Michael