| |
In lugnet.cad.dat.parts.primitives, Steve Bliss wrote:
> One real problem is PARTS.LST. This file is defined in a fixed-width form,
> where the part numbers are only allowed 8 characters. I believe some programs
> (such as MLCAD?) depend on PARTS.LST. So some backwards-compatible solution
> would be needed to shoe-horn 21.3 filenames into the existing PARTS.LST format.
When the LSC updated the spec to allow 21.3 filenames, I don't think any of us
were aware that this would create a problem for PARTS.LST. However, looking at
the file, there's a chance that MLCAD will work perfectly well with longer
filenames inside it. The part name text for those lines would start out in the
wrong place, but depending on how it is parsed, that may not be an issue. It
should be straightforward to test.
--Travis
|
|
Message has 1 Reply:
 | | Re: 11-16 primitives?
|
| (...) Were any other issues anticipated? (...) I did a short test of MLCAD with a modified PARTS.LST. The results were mixed - MLCAD seems OK using an altered-format PARTS.LST file, but re-generating PARTS.LST from MLCAD results in an invalid file. (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)
|
Message is in Reply To:
| | Re: 11-16 primitives?
|
| (...) Parts Tracker-wise (if I remember right, and if nothing's been changed), there's only one script which needs to be modified to accept 21.3 files instead of 8.3 files. Organizationally, I dunno if there is actually a hold-up. The specifications (...) (15 years ago, 25-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
|
|
|
|
