 | | Re: Color page updated
|
|
(...) Do you mean that original LDraw accepts color 48, 65, 133 without error message? I didn't know that. Pity L3Lab (and L3P v1.3 which I no longer use)don't act that way. If so, I guess I stand corrected. And blushing. But yet, with a little (...) (15 years ago, 4-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) Just to be clear: all colors from 0 to 511 (except 16 and 24) are true LDraw colors. For color codes less than 256, LDraw would use the lowest 4 bits to determine the color value. The sixth bit would determine transparency. The other bits were (...) (15 years ago, 4-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) I for one would have been very happy with that approach. That's exactly what I have tried to tell over and over and over again. Could those of you who have their intellectual write protection on, pretty pretty please unlock it for just a few (...) (15 years ago, 4-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
Nobody ever listens to me on the issue of colors, but that doesn't mean I'll go quietly... (...) I don't see why they need to be added to the ldConfig file as long as they're documented somewhere and accepted as the standard default LDraw pallette. (...) (15 years ago, 4-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) Sorry, but I really cannot understand the need to encode dithered colors. Personally I think that only colors used for parts should be coded, while, when you create a patterned part you can choose to use a "good enough" already coded color or (...) (15 years ago, 4-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | 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)
|
