 | | "Tore's" boxes, special file naming instructions
|
|
This is regarding the "officialization" of Tore's boxes (I'll call them ttore boxes, for short), and the making of new boxes have no corresponding Lego part. I was wondering if anyone had any suggestion on how I should name the files of new boxes I (...) (23 years ago, 10-Sep-01, to lugnet.cad.dat.parts)
|
| |
| | Re: "Tore's" boxes, special file naming instructions
|
|
Not a full suggestion, but just a thought. I've thought about calling them "minimized" parts, and maybe the extention .min intead of .box. There is a problem though. I have two different areas in which I could use different levels of simplification: (...) (23 years ago, 11-Sep-01, to lugnet.cad.dat.parts)
|
| |
| | Re: "Tore's" boxes, special file naming instructions
|
|
Tore: (...) Except that the extensions "box" and "min" don't seem to correspond to the two concepts, it might be a good idea to identify the simplification level based in the file name extension. But since the file format is (I assume) still the (...) (23 years ago, 12-Sep-01, to lugnet.cad.dev, lugnet.cad.dat.parts)
|
| |
| | Re: "Tore's" boxes, special file naming instructions
|
|
I looked in the primitves directory and saw that some of the files in the 48 directory had the same filename as those in the P directory. How does Ldraw/Mlcad differentiate between these files? If 3001.box is renamed to 3001.dat, and I place it in (...) (23 years ago, 13-Sep-01, to lugnet.cad.dev)
|
| |
| | Re: "Tore's" boxes, special file naming instructions
|
|
(...) Currently MLCad takes files from the following directories in the order shown below: 1) BFC\P 2) BFC\Parts 3) P 4) Parts 5) Models 6) Current directory (that is the directory where a project has been loaded from or saved to). All other (...) (23 years ago, 13-Sep-01, to lugnet.cad.dev)
|
| |
| | Re: "Tore's" boxes, special file naming instructions
|
|
(...) I'm still thinking about this. Awhile ago, there was discussion of having a "0 DETAIL" meta-statement, to identify which lines in a DAT were critical for rendering, and which lines filled in the details. This approach could be used to reduce (...) (23 years ago, 13-Sep-01, to lugnet.cad.dat.parts)
|
| |
| | Re: "Tore's" boxes, special file naming instructions
|
|
(...) After a year or so of thinking - well I have thought of other things, too :) - I have come to a decition that suits me and my needs. I work with large .DAT models (Datsville) and I mainly use my own utilities towards L3Lab and L3P. I suppose (...) (22 years ago, 30-May-02, to lugnet.cad.dev, lugnet.cad.ray)
|
