 | | 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
|
| (...) 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 don't know how ldglite and other parsers work, but I guess they don't create files with paths and all, but rather objects somewhere in RAM, with 'filenames' just as a property. But if you call the procedure SaveToFile(Path+FileName) to save (...) (22 years ago, 6-Aug-02, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
| | | | | Re: MPD spec
|
| (...) Right. Any "MPD splitter" program should include code to check that filenames and paths are valid, and either report missing paths, or create them, or ask the user before creating them, or provide options (ie, command line parameters) to (...) (22 years ago, 6-Aug-02, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
| |
