| |
In lugnet.cad.dat.parts.primitives, Steve Bliss wrote:
> In lugnet.cad.dat.parts.primitives, Don Heyse wrote:
>
> > I could update the mklist sources to work handle filenames with 25 chars
>
> That would be good, I think.
>
> > I was going to add a quietmode commandline option this weekend anyhow.
>
> Can you have two levels? Level One that still shows the warnings, but
> doesn't stop, and Level Two suppresses all warnings.
Yeah, I was actually planning a -f to force it to finish and -q for quiet.
> > Should I allow 25 chars as the default, and perhaps include an optional
> > command line arg to force/truncate it to 12 chars for backwards
> > compatibility with old programs?
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 the filenames, which should work ok for DOS/Windows,
but looks kinda ugly.
> I'd keep the current line-format for all parts conforming to the 8.3
> format, but for longer names, print the entire filename, a space, and
> the description. Like this:
>
> 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.
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?
Don
|
|
Message has 2 Replies:
 | | 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)
| | | 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)
|
Message is in Reply To:
| | Re: 11-16 primitives?
|
| (...) That would be good, I think. (...) Can you have two levels? Level One that still shows the warnings, but doesn't stop, and Level Two suppresses all warnings. (...) I'd keep the current line-format for all parts conforming to the 8.3 format, (...) (15 years ago, 27-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
|
|
|
|
