|
| | New version of MLCad command spec
|
| Hi, there is a new draft version of the MLCad command spec available for download at (URL) is in version V1.1 state draft. Please feel free to comment this document. I have rewritten the lizence section and added a section for the rotation points. (...) (22 years ago, 6-Aug-02, to lugnet.cad.mlcad)
| | | | 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)
| | | | Re: MPD spec
|
| (...) Another thing I realised the other day is that in Australia, the opposite of clockwise is generally anti-clockwise rather than counter-clockwise, so the BFC CERTIFY should really be CW or ACW, but it's a bit late to worry about it now! ROSCO (22 years ago, 6-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)
| |