|
|
Unofficial File parts/71016.dat
Next File |
Prev File |
Download |
Review |
Edit |
CA Header Edit |
Events
File Header:
0 _Minifig Helmet Visor Space [334]
0 Name: 71016.dat
0 Author: [PTadmin]
0 !LDRAW_ORG Unofficial_Part Physical_Colour
0 !LICENSE Redistributable under CCAL version 2.0 : see CAreadme.txt
0 BFC CERTIFY CW
0 // This file is a "shortcut" with the correct number for the actual
0 // colouring of the part (Chrome Gold).
Status:
1 'hold' vote. (CCCHX)
Size: 373 bytes
Reviewers' certifications:
Philo=certify
Steffen=certify
arezey=novote
dulcaoin=certify
mikeheide=novote
westrate=hold
Required (unofficial) subfiles:
(none)
Related (unofficial) files:
(none)
File reviews and updates:
At Fri Mar 2 12:44:14 2007, the file was initially submitted.
Submitted by: cwdee
======================================================================
At Sat Mar 3 06:34:06 2007, the following review was posted:
Reviewer: dulcaoin
Certification: certify
No comments were posted with this review.
======================================================================
At Sat Mar 3 09:04:05 2007, the following review was posted:
Reviewer: mikeheide
Certification: certify
No comments were posted with this review.
======================================================================
At Fri Jun 12 09:56:04 2009, the following review was posted:
Reviewer: mikeheide
Certification: hold
Comments:
There is a part number issue. Please see comments on http://www.ldraw.org/cgi-bin/ptdetail.cgi?f=parts/23318.dat
======================================================================
At Fri Jun 12 10:10:02 2009, the following review was posted:
Reviewer: mikeheide
Certification: hold
Comments:
Item number for chrome gold hard colored is 4125104.
Design number for that is 71016.
======================================================================
At Fri Jun 12 11:46:01 2009, the following review was posted:
Reviewer: Philo
Certification: certify
Comments:
This one is OK! 71016 _is_ chrome gold.
======================================================================
At Fri Jun 12 14:40:05 2009, the following review was posted:
Reviewer: mikeheide
Certification: hold
Comments:
I am not convienced.
Our part numbers are DESIGN numbers with color 16 (normally).
For some parts we know the ITEM number and that parts get colored, are parttype 'Shortcut Physical_Colour' and a leading '_' in partdescription.
I agree that the number 71016 is the design number for but not the item number.
So this file is incorrect.
======================================================================
At Fri Jun 12 14:50:17 2009, the following review was posted:
Reviewer: Philo
Certification: hold
Comments:
Agreed, but for _some_ parts (including metallized parts like this one), LEGO has a design number for each color. 71016 IS chrome gold (and 23318 IS chrome blue)
======================================================================
At Fri Jun 12 15:18:02 2009, the following review was posted:
Reviewer: Philo
Certification: certify
Comments:
...wrong checkbox, I meant Certify!
======================================================================
At Fri Jun 12 17:16:07 2009, the following review was posted:
Reviewer: mikeheide
Certification: novote
Comments:
If I follow your argumentation, then part no. 23318 needs to be colored 'chrome blue' and we do not have any part of this type without a fixed color.
I downgrade to novote because I can live with that, but it is against all we have done in the past and described in our rules.
======================================================================
At Fri Jun 12 17:24:04 2009, the following review was posted:
Reviewer: Philo
Certification: certify
Comments:
Yes. Would be nice if an admin chimed in...
======================================================================
At Fri Jun 12 19:42:13 2009, the following review was posted:
Reviewer: Steffen
Certification: novote
Comments:
I think this can easily be resolved:
a) create a part x...dat containing the un-colored version
b) make all part numbers that explicitly contain a color
use that part and let them just hard-code the color
c) make all parts of b) Color Shortcuts
======================================================================
At Fri Jun 12 19:42:13 2009, the following review was posted:
Reviewer: Steffen
Certification: hold
Comments:
upgrading to hold
======================================================================
At Sat Jun 13 05:52:01 2009, the following review was posted:
Reviewer: Philo
Certification: certify
Comments:
Another solution would be to create two generic color parts (23318 and 71016) using proper -c command line
======================================================================
At Sat Jun 13 07:32:02 2009, the following review was posted:
Reviewer: mikeheide
Certification: novote
Comments:
That is what I was talking about for a while ;-)
======================================================================
At Sat Jun 13 08:16:11 2009, the following review was posted:
Reviewer: arezey
Certification: novote
Comments:
Another one I can make up would be to make 71016.dat an alias of 23318.dat and make the two Physical_Colour parts (4125104.dat and whatever the other one is).
======================================================================
At Sat Jun 13 08:16:11 2009, the following review was posted:
Reviewer: Philo
Certification: certify
Comments:
Then... I misunderstood. Sorry ;o)
======================================================================
At Sat Jun 13 09:30:06 2009, the following review was posted:
Reviewer: mikeheide
Certification: novote
Comments:
And if you make the colored parts you have to be aware of the file your reference. Then we have what I have searched for and we are fine also with our rules.
======================================================================
At Sat Jun 13 10:38:02 2009, the following review was posted:
Reviewer: Steffen
Certification: hold
Comments:
Let me summarizethe discussion here:
the 2 possible solutions for this are:
I) Have one color-16 part x....dat plus two Physical_Color shortcuts
to it
II) Have two identical parts which just differ in the !CMDLINE
statement. Maybe put the common part geometry into a subfile.
I have a clear preference of solution I). Reason:
Solution II) is a way to implement Physical_Color "shortcuts"
via subfiling. It wouldn't match the way all our other
Physical_Color shortcuts are constructed: All these follow
solution I).
======================================================================
At Thu Jun 17 20:05:03 2010, the following review was posted:
Reviewer: Steffen
Certification: hold
Comments:
additionally, please cf. 4505182.dat which names the color
"MetallicGold" which I also do not like. I would like better
"Gold Metallic" or "Metallic Gold".
This file currently uses "Chrome Gold" which I plainly do not understand. It's like "Wood Plastic" or "Water Gasoline" to me.
======================================================================
At Tue Nov 9 16:40:14 2010, the following review was posted:
Reviewer: westrate
Certification: hold
Comments:
Steffen said:
I) Have one color-16 part x....dat plus two Physical_Color shortcuts
to it
There already is a color 16 version of this part: 769.dat. The "Moved to" version on the tracker is incorrect, and should be deleted. Once that is done, there is no problem with this file.
======================================================================
At Fri Aug 10 05:35:05 2012 a Parts Tracker Admin edited the header.
======================================================================
At Fri Aug 10 11:30:03 2012, the following review was posted:
Reviewer: Steffen
Certification: certify
No comments were posted with this review.
======================================================================
At Fri Aug 10 11:35:02 2012, the following review was posted:
Reviewer: Steffen
Certification: certify
Comments:
the mentioned change has happened now.
please certify.
|