 | | 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)
|
| |
| | Re: Renaming of 2916.dat
|
|
(...) It might. (...) I can see your point. And I must admit that the first category I would search for this part under would be "Train". - Which certainly implies that "train" at least should be a keyword for the part. (...) Sort of. In principle (...) (22 years ago, 24-Jul-02, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Renaming of 2916.dat
|
|
(...) It is not my intention to control the fate of this part forever and ever. But to have some input as to how it is categorized and where it ends up in the parts list. (...) (22 years ago, 24-Jul-02, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Renaming of 2916.dat
|
|
(...) I would argue that 2917 probably belongs in windscreen or window, I guess? In an ideal world there would be a way to associate a part with its "partner" as it were without using naming, there just would be a link between them somehow. (...) (22 years ago, 23-Jul-02, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Renaming of 2916.dat
|
|
(...) True, but I feel this part might fall under Larry's "terribly unwieldy" escape clause. Even if he doesn't think so. (...) It's arguable at this point, but the long-term general idea is that you can do whatever you want with your original file, (...) (22 years ago, 23-Jul-02, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: File Header request for Minifig Parts
|
|
BTW, I found part of that discussion I mentioned in my other post. Here's the text. I don't think Terry will mind me posting it. The file I found this in is dated 7/5/2001, the discussion is possibly a year older than that. Some things are out of (...) (22 years ago, 23-Jul-02, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
