 | | Re: General Comments to MLCad
|
|
(...) Could you avoid writing out the file as a ".DAT" file extension if you are making extensions to the long established LDraw DAT file format? This would clear up confusion right away and avoid further incompatibility issues if other LDraw-clone (...) (25 years ago, 19-Dec-99, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| |
| | Re: hex values (was: Re: Loader)
|
|
I thought LDLite is able to display this colors! If this is realy a problem I can change this to use comment lines defining these custom colors! Todd Lehman wrote in message ... (...) (25 years ago, 19-Dec-99, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: OMR Planning - Almost There
|
|
(...) Hee. :) (...) Yeah. (...) We could ask for all the model info, and the server will create the header with the submission. But then what about submodels? They'd need to have headers cause we can't have a bazillion fields for the separate (...) (25 years ago, 19-Dec-99, to lugnet.cad.dev.org.ldraw)
|
| |
| | hex values (was: Re: Loader)
|
|
(...) Wonderful. So why does MLCad insert nonstandard data into LDraw DAT files? --Todd (25 years ago, 19-Dec-99, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: OMR Planning - Almost There
|
|
(...) faux pa (although the "paw" bit is funnier) (...) Unfortunately, not everyone is going to get the model header right, so you'll probably need (required) fields for name, email, etc. The only problem is that you most likely want a comments (...) (25 years ago, 18-Dec-99, to lugnet.cad.dev.org.ldraw)
|
