 | | Re: Official Parts using MLCad colors
|
| Hi, Scott Wardlaw has written a prog which matches the colors used in the official parts against the now updated LDConfig.ldr colors chart. This is a list of parts that use colors which were mainly defined in MLCad and have never been LDraw colors: (...) (17 years ago, 30-Sep-09, to lugnet.cad.dat.parts, lugnet.cad.dev.org.ldraw)
| | | | | Re: 11-16 primitives?
|
| (...) In the mklist beta I posted there's an undocumented -r switch to turn off the ragged edges and make room for 25 char filenames. There's also an undocumented -t to twiddle with the 78 vs 80 character line formats. But there's nothing yet for (...) (17 years ago, 29-Sep-09, to lugnet.cad.dat.parts.primitives)
| | | | | Re: 11-16 primitives?
|
| Sorry to follow-up my own post, but I did a quick test on MLCAD. (...) I had a DUH! moment after posting the previous message. If MLCAD can use a ragged format file, of course it can use a fixed-25 format file. DOH. (...) I prepared a PARTS.LST file (...) (17 years ago, 29-Sep-09, to lugnet.cad.dat.parts.primitives)
| | | | | mklist 1.6beta1
|
| (...) I'm assuming the 80 char lines is what you're aiming for here, so based on the 64 char limit on descriptions I started the descriptions on the 16th character of the line. That gives room for a 15 character name and a single space before the (...) (17 years ago, 29-Sep-09, to lugnet.cad.dat.parts.primitives)
| | | | | Re: 11-16 primitives?
|
| (...) My thinking is the 'ragged' format has the least impact - if there are no long part nambers, then the output PARTS.LST would exactly match the classic format, without the user having to know anything about long/short part nambers. Of course, (...) (17 years ago, 29-Sep-09, to lugnet.cad.dat.parts.primitives)
|
|
