|
|
 | | Re: MPD spec
|
| (...) FWIW both the ldlite and l3 parsers in ldglite are OK with paths in an MPD file. Just make sure the path in the 0 FILE line matches the path on the type 1 line that pulls in the subfile. If they don't match it reports that it can't find the (...) (22 years ago, 6-Aug-02, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
| | | | | 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)
| | | | | Re: MPD spec
|
| (...) Hmm. I don't remember if there was a lot of discussion about putting paths on the 0 FILE line. So I won't say for absolute sure that the program should allow them. I'd say any software that *thinks* it needs a directory, and crashes when it's (...) (22 years ago, 5-Aug-02, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
| | | | | Re: MPD spec
|
| (...) Err, the entry for MPD in the glossary: (URL) here: (URL) is a bad link. Could you update the glossary to point to the new spec? Don (22 years ago, 5-Aug-02, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
| | | | | Re: MPD spec
|
| (...) MPD Workshop cannot handle a reference to a non-existing directory, or rather, it does not create a folder if necessary. For example: (URL) line: 0 FILE s\41342s01.dat assumes that there already exists the folder 's\' in the target directory, (...) (22 years ago, 5-Aug-02, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
|
