| |
In lugnet.cad.dat.parts.primitives, Don Heyse wrote:
> In lugnet.cad.dat.parts.primitives, Steve Bliss wrote:
> > 3001.dat Brick 2 x 4
> > 3001c01p01.dat Brick 2 x 4 Some Variation with Pattern
> > 3002.dat Brick 2 x 3
> >
> > A backwards-compatibility switch is good -- maybe with option to
> > truncate (or not) the description to fit 80 bytes per line?
>
> Ok, I'd like to know what you're thinking here. The specs say 25 chars
> in the filenames, and I don't really like a ragged left edge on the
> descriptions, both visually and because it complicates the sorting code.
> So tell me why someone might want that, especially as more long
> filenames get released. It's gonna look awful.
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, if further MLCAD tests shows that it works with a fixed-format 25
char filename column, then there's less reason to go with the ragged format.
> Right now, mklist always truncates the description to 64 chars, which
> fits on an 80 char line with the 8.3 filenames. I take it you'd like to
> (optionally?) make it instead truncate the filename+space(s)+description
> to 80 chars when using long filenames. Is there some program that this
> will help, or is this so it still fits in an 80 char terminal window?
I was thinking that some old programs depend on the rigid 80 byte record format,
but most programs are line-delimited, and don't care about the exact line
length. Over time, we've seen an increased need for longer, more detailed part
descriptions. In some cases, the 64 char description limit is already an issue
for part naming. For example, a number of the 6100 patterned baseplates break
the 'with ... Pattern' naming convention.
So it would be nice to be able to produce a PARTS.LST with full descriptions if
rigid conformance to 80-byte records is not needed.
Steve
|
|
Message has 1 Reply:
 | | 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)
|
Message is in Reply To:
| | 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)
|
22 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
