| |
In lugnet.cad.dev, Roland Melkert writes:
> 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.
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
|
|
Message has 2 Replies:
 | | Re: MPD spec
|
| (...) I don't know about the other parsers, but as far as LDView is concerned an LDraw file is an LDraw file is an LDraw file. It makes no distinctions between ldr files, dat files, and mpd files. If it sees a 0 FILE command, it starts its MPD (...) (22 years ago, 6-Aug-02, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
Message is in Reply To:
| | Re: MPD spec
|
| 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 (...) (22 years ago, 5-Aug-02, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
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
|
|
|
|
