 | | Re: Description of MLCad extensions available now
|
|
(...) Uh Oh, we need some *unlicensed* documentation on this meta command. It's already used in some official parts. If I have to get permission in writing to use all the features of the official parts (or be liable for unspecified damages) I'm (...) (22 years ago, 29-Jul-02, to lugnet.cad.mlcad, lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: File Header request for Minifig Parts
|
|
hi steve, (...) many thx for the hint. (...) are we takling about categories like "brick" and "plate" or sub-categories, which will need a renaming of the header? probably the fact that I just use MLCad causes some misunderstanding. I can't see a (...) (22 years ago, 25-Jul-02, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: ASSOCIATE (was: Re: Renaming of 2916.dat)
|
|
(...) WAY better than using naming to overload. 2916 and 2917 get at best a very weak association if they have train in their name. With the ASSOCIATE keyword extension it becomes quite explicit what their connection is. (and parts can also have (...) (22 years ago, 24-Jul-02, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: ASSOCIATE (was: Re: Renaming of 2916.dat)
|
|
(...) Yes. Play well, Jacob (22 years ago, 24-Jul-02, to lugnet.cad.dev.org.ldraw)
|
| |
| | ASSOCIATE (was: Re: Renaming of 2916.dat)
|
|
(...) Hmm. Interesting idea. So part 3937 (URL) might have an entry like: 0 ASSOCIATE 3938 6134 and part 3938 (URL) might have: 0 ASSOCIATE 3937 2440 (of course, these examples capture information that otherwise might be captured by a connectivity (...) (22 years ago, 24-Jul-02, to lugnet.cad.dev.org.ldraw)
|
