|
|
 | | Re: Color page updated
|
| (...) It might fix it (I think it would still gum up the PT with over-zealous hold votes); but why break anything when we're just talking about adding fewer than 200 lines to the config file? I think it's a terrible idea to make dozens of (...) (15 years ago, 4-Dec-09, to lugnet.cad.dev.org.ldraw, FTX)
| | | | | Re: Color page updated
|
| (...) I have had parts on the Part Tracker held because they used one of these colors. That means it is limiting. (...) Color numbers 32-47 and 256-511 is not every color under the rainbow. (...) This is exactly the problem. (...) If this is the (...) (15 years ago, 4-Dec-09, to lugnet.cad.dev.org.ldraw)
| | | | | Re: Color page updated
|
| (...) There are already two very old ways to specify RGB colors in LDraw files. One comes from ldlite with somewhere between 12 and 15 effective bits of color information, and the other from L3Lab/L3P with 24 bits of color information. If we're (...) (15 years ago, 3-Dec-09, to lugnet.cad.dev.org.ldraw, FTX)
| | | | | Re: Color page updated
|
| (...) Of course it would - as well as it does LDView. But after adding x, y, z coordinates and correcting RGB code syntax would work fine with both LDView as well as L3Lab! 1 0x02F2F2F2 0 0 0 1 0 0 0 1 0 0 0 1 part.dat Don't know about MLCad, but I (...) (15 years ago, 3-Dec-09, to lugnet.cad.dev.org.ldraw)
| | | | | Re: Color page updated
|
| (...) Neither did I but if you really cannot find a suitable color for your pattern an RGB say in the form: 1 #F2F2F2 1 0 0 0 1 0 0 0 1 part.dat would surely solve your problem. And I'm going to propose this to the new elected LSC. As for the broken (...) (15 years ago, 3-Dec-09, to lugnet.cad.dev.org.ldraw, FTX)
|
|
