Subject:
|
Re: Part Numbering Crisis in LDraw
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Sat, 27 Feb 1999 03:39:31 GMT
|
Viewed:
|
1498 times
|
| |
|
|
On Fri, 26 Feb 1999 21:47:44 GMT, Karim <knassar@mindspring.com> wrote:
> Terry K wrote:
>
> > The problem is, that some elements would force us to use numbers in seemingly
> > un-intuitive ways. An example:
> >
> > The yellow dinghy in the vote is numbered 30086. That is the imprinted number
> > for the lower portion only. The top is 30087. The aggregate number for both
> > is 4106548. But that number is _only_ for the yellow version.
> > Any other color (like tan) would be different.
>
> It seems to me that the only reason on TLG's part to have 2 seperate numbers and
> then one different aggregate number for a specific color is to provide for a
> situation in which the two pieces are different colors (ie: black top, yellow
> bottom). That's the only reason that make sense to me to have such a screwy
> numbering scheme. Given that, maybe we should enter the boat as 2 seperate pieces
> (top and bottom) 30086 and 30087 with a shortcut hard-coded in yellow called
> 4106548. In the off-chance that TLG ever releases a set with different colors, we
> can then worry about whether to release a new part or just stay with the 3 files.
>
> --Karim
The problem with that solution is that we would then have the 4106548 hard
coded as yellow. And when the tan version is released are we then going to
have another 410xxxx for it - hard coded to tan?
That may not seem like a big deal, until you think about using this method for
other parts - parts that may well come in many colors. Then, using that
method, we would end up with a lot of duplicate parts in different colors.
This would lead us down the road to having multiple versions of parts. I would
prefer to have one basic version of the part, color being user-selectable.
-- Terry K --
|
|
Message has 3 Replies:
 | | Re: Part Numbering Crisis in LDraw
|
| (...) Is it not possible to say in the definition of 410etc., like: top half yellow, lower half yellow underneath. That way, the only information in the 410etc file is the color, and which constituents parts there are. Then if anything needs to (...) (25 years ago, 27-Feb-99, to lugnet.cad.dev)
| | | Re: Part Numbering Crisis in LDraw
|
| (...) I concur. Part of the beauty and flexibility of LDraw is that you can model with parts in colors that those parts don't come in. Once we start down the road of having parts hard coded only in the color(s) they really exist in, we limit our (...) (25 years ago, 27-Feb-99, to lugnet.cad.dev)
| | | Re: Part Numbering Crisis in LDraw
|
| Terry K (legoverse@geocities.com) comments Karim's "30086.dat" and "30087.dat" in colour 16, and "4106548.dat" in yellow/yellow suggestion (which I support): (...) Yes. The problem is that this is a multi-mold part which is likely to appear in (...) (25 years ago, 5-Mar-99, to lugnet.cad.dev)
|
Message is in Reply To:
| | Re: Part Numbering Crisis in LDraw
|
| (...) It seems to me that the only reason on TLG's part to have 2 seperate numbers and then one different aggregate number for a specific color is to provide for a situation in which the two pieces are different colors (ie: black top, yellow (...) (25 years ago, 26-Feb-99, to lugnet.cad.dev)
|
66 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
|
|
|
|
