 | | numbers for "Castle" minifig torso patterns?...
|
|
Chris, In a message you sent to me some time ago, you had mentioned that the "range" of "p40" to "p50" was set aside for the patterns from "Castle". However, I just noticed that we've used all but one of these pattern numbers for the minifig torsos. (...) (24 years ago, 29-Nov-00, to lugnet.cad.dev)
|
| |
| | Re: numbers for "Castle" minifig torso patterns?...
|
|
(...) Based on recent discussions here, I think we have agreed to allow alpha characters after the "p", to prevent pxx number expanfding to three digits (not a problem for 973pxx, but potentially for 3626bpxx and similar). That means that we can (...) (24 years ago, 29-Nov-00, to lugnet.cad.dev)
|
| |
| | Re: numbers for "Castle" minifig torso patterns?...
|
|
(...) I remember it being discussed, but I don't recall any agreement. The flaw I saw with this proposal is, is the file "973p4a.dat" an independent part all its own, or is it merely the first _sub_part of "973p4.dat"? The more I've been thinking (...) (24 years ago, 29-Nov-00, to lugnet.cad.dev)
|
| |
| | Re: numbers for "Castle" minifig torso patterns?...
|
|
(...) I see three reasons why this argument may be flawed, but I think we are confusing the meaning of subpart. 1) The Pxx number are all two digits, so 973p4.dat should never exist. 2) The same pattern on a part varient would be demand a suffix for (...) (24 years ago, 29-Nov-00, to lugnet.cad.dev)
|
| |
| | Re: numbers for "Castle" minifig torso patterns?...
|
|
(...) I'm still not sure about using 'S' for this, because S01 is commonly used for parts/s/ files. But I definitely agree with the idea. (...) Erk. Doesn't LEdit cut off file-references that a too long? (...) Authors have got to be careful to (...) (24 years ago, 1-Dec-00, to lugnet.cad.dev)
|
