To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.devOpen lugnet.cad.dev in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Development / 330
329  |  331
Subject: 
Part Numbering Crisis in LDraw
Newsgroups: 
lugnet.cad.dev
Date: 
Fri, 26 Feb 1999 02:05:00 GMT
Viewed: 
1077 times
  
Everyone,

We are facing a major problem in numbering parts in LDraw.  For quite some time
I have been trying to follow a 3 rule plan for numbering pieces:
1.  Full accuracy when possible
2.  Use official TLG numbers if we have them
3.  Use temporary 3-digit numbers for unkowns.

Sounds simple, right?

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.

So what to do?
   Keep the imprinted number on the bottom as THE number?
   Use the 4106548 as THE number for all versions?
   Use the 4106548 for the yellow version, and add a tan one later?
   Give up and give it a 3-digit number and ignore all other numbers?


Some more problems from the current vote:  (from Joshua Delahunty)
-----
81155 is always black, with a yellow pattern
80394 is always white, with a fixed color pattern
30208 doesn't (shouldn't?) have the number 30208 with this year's
           introduction of a gold version.
71427 is always grey (and black).
81038 is always red, with fixed color pattern
70749 and 70750: always chrome
70496, always black (though I think you're safe here)
81890 is always white
81174 is always yellow
------

So, you can see we are faced with many problems.
Using a strictly enforced accuracy rule will force us to have multiple versions
of the same part, in different colors.

What to do?
We need to resolve this as a group decision.

-- Terry K --



Message has 8 Replies:
  Re: Part Numbering Crisis in LDraw
 
(...) This is my vote. If 4106548 is always yellow, without exception, hard-code the yellow color in the .DAT. (but see below) A possibly more sensible alternative is to do parts 30086 and 30087 each as color 16, and do a (...) (25 years ago, 26-Feb-99, to lugnet.cad.dev)
  Re: Part Numbering Crisis in LDraw
 
(...) Hmmm.. well, we *could* have them all... use 30086 and 30087 as the two parts of the dinghy... then have part 4106548 simply reference the two "subparts" and have this "element model" hard-coded in yellow... anyone wanting to use a different (...) (25 years ago, 26-Feb-99, to lugnet.cad.dev)
  Re: Part Numbering Crisis in LDraw
 
(...) time (...) Some things to think about: It would be irritating in Ldraw to have to page through lists that look like this: xxxxx.dat Blah blah blah X blah Tr. Yellow-Green yyyyy.dat Blah blah blah X blah Gold zzzzz.dat Blah blah blah X blah (...) (25 years ago, 26-Feb-99, to lugnet.cad.dev)
  Re: Part Numbering Crisis in LDraw
 
Terry K wrote in message <36d5fd53.5480877@lu...et.com>... (...) seemingly (...) number (...) both (...) I thought you had to break the two halves apart to get at the 30087 number. Do you have to break it apart? If so can you use them afterward? If (...) (25 years ago, 26-Feb-99, to lugnet.cad.dev)
  Re: Part Numbering Crisis in LDraw
 
(...) I am *SOOO* happy that Terry and Joshua (and others) are anal-retentive enough and pedantic enough -- and thorough enough -- to bring this sort of thing up. Just imagine what a mess it would all be if nobody cared... This is really cool, guys! (...) (25 years ago, 26-Feb-99, to lugnet.cad.dev)
  Re: Part Numbering Crisis in LDraw
 
(...) Damn. They noticed. After the chrome antenna fiasco, I swore to keep my mouth shut, and not point out potential part-number mixups. Actually, I forgot all about that little trivial bit of part-numbering reality on the obviously (...) (25 years ago, 26-Feb-99, to lugnet.cad.dev)
  Re: Part Numbering Crisis in LDraw
 
(...) In this case, I say use the number stamped on the part. (...) Did we decide to move away from the xxxxPxx format? This sounds like a good reason to rethink that decision. Not that I expect this particular element to ever resurface in a (...) (25 years ago, 26-Feb-99, to lugnet.cad.dev)
  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
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR