Hi Micha,
> If you would add ini options for displaymesh-to-3dm save,
> than no user who don't need it would get a large file.
Yes, that's true! But it's not simply a matter of making an .ini file flag, features like putting the display mesh into the 3DM file require me to code them, I don't just set a flag and the feature pops up in MoI automatically... :)
It can be hard to justify spending time on a particular feature that is totally hidden from regular use by only being accessed by an .ini option.
.ini options are normally better used for things that are a modification in behavior of existing features.
I do have exporting a 3DM mesh file on my list of things to look at in the future, but it's unfortunately an awkward thing to integrate into the regular UI. Having 2 different kinds of 3DM files listed in the regular file types dropdown could easily lead to confusion, with one 3DM variation being MoI's main save type, and the other mesh variation being a completely different type of data that could actually not even be read back into MoI. There is potential there for someone to actually lose their data by mistakenly saving to the wrong 3DM variation.
So probably at some point it will be something that could be accessed by script, and if I had a script library UI that people browse though scripts more easily that would then make it a more accessible thing than only enabled by the .ini file.
I'm not sure when I will be able to work on these various pieces that would go into that though.
- Michael
|
