|
|
 | | Re: Color page updated
|
| (...) Tore, Feel free to add any color, RGB, name or number you like to the LDConfig.ldr. file. I really won't stand in the way of 100% backwards compatibility to L3Lab. w. (15 years ago, 5-Dec-09, to lugnet.cad.dev.org.ldraw)
| | | | | Re: Color page updated
|
| (...) Oh. Oh. I... I wish somebody had told me this before, instead of arrogant and provoking things like: "Welcome to 2009". Or maybe someone has tried, but I've been the write protected that time? /Tore (15 years ago, 5-Dec-09, to lugnet.cad.dev.org.ldraw)
| | | | | Re: Color page updated
|
| (...) Yes, exactly. 48 is rendered as trans-black, 65 is blue, and 133 should be dark pink (or whatever we're calling color #5 today). Steve (15 years ago, 5-Dec-09, to lugnet.cad.dev.org.ldraw)
| | | | | 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)
|
|
