(2018-12-01, 6:08)Orion Pobursky Wrote:(2018-12-01, 4:59)Travis Cobbs Wrote: I also don't understand what you mean by auto-generated fallback code. LDView doesn't support any of these metas, but it was my understanding that they were designed to be used by the editor to then generate standard LDraw geometry. So only editors would have any need to support them. Am I missing something important?
Fallback code is optional. The entire part can be generated and displayed by the editor using only the info in the METAs. I believe LDCad actually does this and only generates the fallback code if requested. Where the fallback code is useful is for legacy editors.
I don't think "fallback" is the correct term here. I think "results" is a much closer term to what you mean, unless I'm still misunderstanding. The META commands indicate how a flexible part should be generated, but in order to have an LDraw file, the editor needs to actually do the generation and create an LDraw file with geometry. And it seems to me that this is not at all optional. Put bluntly, I never plan to support any of these METAs in LDView, and I don't think it's appropriate for flexible parts not to display at all in LDView simply because it doesn't support these META commands.
Maybe I'm still totally misunderstanding what you mean.