| |
I was wondering, didn't see it discussed in the text, is it permitted /
custom to have ldraw files in a mpd file reference other mpd files?
If so is the first part in the file used or is there some naming
convention pointing to the correctsubpart (e.g. brick.mpd:1x1.dat).
Or do you just recursive load all mpd files to memory and then start
parsing the parts with their original names. But this kinda contradicks
the text saying to only parse references parts.
Roland
Steve Bliss wrote:
> In lugnet.cad.dev, Jacob Sparre Andersen writes:
>
> > Rui:
> >
> >
> > > I'm still searching for the spec !
> >
> > See <URL: http://hugin.ldraw.org/meyer/LEGO/V%E6rkt%F8j/#MPD.Files >.
> > You are welcome to try to make it easier to understand.
>
>
> Jacob,
>
> Do you mind if I copy (and update) the information on your MPD page to
> www.ldraw.org/reference/specs?
>
> Steve
>
|
|
Message has 2 Replies:
 | | Re: MPD spec
|
| (...) This is a very good question, and is even more important with the migration to a single filename suffix (.LDR). What happens when your type-1 line refers to a LDR that happens to be a multi-part dat? Cheers, - jsproat (22 years ago, 6-Aug-02, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
| | | Re: MPD spec
|
| (...) Good question. Different programs have more (or less) success at handling this. L3Lab seems to have no trouble with it. LDLite usually does ok, but not always (unfortunately, I don't have an example). (...) There's no special syntax, the (...) (22 years ago, 6-Aug-02, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
Message is in Reply To:
65 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
