|
|
 | | Re: MPD spec
|
| (...) I would even call it a bad thing to do. But then I have a habit of putting "FILE" meta-command in all my files, so maybe I should stop criticising and try to fix my own bad habits first. > It's very easy to overwrite the main file with if the (...) (22 years ago, 6-Aug-02, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
| | | | | Re: MPD spec
|
| (...) I have ldr files with up to 4 levels of nested sub files, and LDview, L3Lab, and MLCad all appear to render them fine. ROSCO (22 years ago, 6-Aug-02, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
| | | | | 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)
| | | | | 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
|
| (...) 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)
|
|
