 | | Re: Open cylinder primitives, any demand?
|
|
(...) Naming is not an important issue to me. Either name would be fine for me. The one important thing for me is that it doesn't mess up with renderers and utilities that make primitive substitutions. But I don't see that there should be any risk (...) (15 years ago, 2-Nov-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Open cylinder primitives, any demand?
|
|
(...) Not being a part author, I can't comment on the utility, but to me the naming is confusing. The base cylinder primitives are already open at both ends; they just don't have edges there. So to me, cyle would make more since in the filename, and (...) (15 years ago, 2-Nov-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Open cylinder primitives, any demand? [DAT]
|
|
Is there any demand for this type of cylinder primitive that's open at both ends? 0 Cylinder open 1.0 0 Name: 4-4cylo.dat 0 Author: Mark Kennedy [mkennedy] 0 !LDRAW_ORG Unofficial_Primitive 0 !LICENSE Redistributable under CCAL version 2.0 : see (...) (15 years ago, 1-Nov-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | 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 (...) (15 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 (...) (15 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 (...) (15 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, (...) (15 years ago, 29-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) Yeah, I was actually planning a -f to force it to finish and -q for quiet. (...) For now I've added a -8 to make it use the 8.3 format. As per Travis' suggestion it converts to the canonical short form under Windows. The function uppercases (...) (15 years ago, 28-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) For MLCAD it doesn't matter. Steve said that MLCAD worked fine with long filenames inside parts.lst. The only reason to put the short filename in is for other programs that might have problems with the long filename. And as long as mklist is (...) (15 years ago, 27-Sep-09, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: 11-16 primitives?
|
|
(...) Sounds easy, but I think nobody can read that short filenames that would appear in the MLCad list!? cu mikeheide (15 years ago, 27-Sep-09, to lugnet.cad.dat.parts.primitives)
|
