 | | Re: Color page updated
|
|
(...) That's good! Anyway, there are still many color codes included in official parts (39,257,258,260...) that seems are not supported. I have already rosen the problem in a previous discussion and the answer was that they where MLCad color codes (...) (15 years ago, 2-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) I started fixing those parts and they will be uploaded to the PT for certification since some also include minor primitive substitution as well as BFCing. However I cannot forseen when those fixes will be ultimately be shipped in an official (...) (15 years ago, 2-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) That's a really good new!!! since something is moving on and that's enough for me. In the while I will translate all missed color codes in the range on transparent colors to a light grey transparent (having code between 32 and 63) and all the (...) (15 years ago, 2-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) That is correct. LDView has its own internal color table, which is used if you don't check the "Process ldconfig.ldr" check box in the General tab of its preferences. When you check that check box, it overrides these default colors using the (...) (15 years ago, 2-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) I apparently have missed the discussion when it comes to certain colors are suddenly "not supported," but I'd like to register my opinion on it. It is a huge error to be calling colors in the ranges of 32-47 and 256-511 as "MLCad color codes" (...) (15 years ago, 2-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) Although I have decided to refrain from participation in this thread (you already know my position and you totally neglect it), I make one exception and say "Amen!" to all of Andy's points above. /Tore (15 years ago, 2-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) This isn't the first time that LDconfig.ldr has been updated - and it is just that, the file has been updated with MORE colors than before. I think we are loosing sight of the purpose of LDconfig.ldr... The LDconfig file is meant to be a quick (...) (15 years ago, 3-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) I disagree that this was the original purpose of the ldconfig file. I can say that definitively, since I was the one who first proposed the file here: (URL). The purpose was that when *new* colors were added, ldraw software tools would have a (...) (15 years ago, 3-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) I never said that it was meant to limit, only that it is made up of these colors now. Please don't take this to mean that new colors can't be added, or that it invalidates other colors. We already know of at least one color that should be (...) (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)
|
| |
| | 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
|
|
(...) 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
|
|
(...) 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
|
|
(...) 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
|
|
(...) 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
|
|
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
|
|
(...) 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
|
|
(...) 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
|
|
(...) 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
|
|
(...) 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
|
|
(...) 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
|
|
(...) 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
|
|
(...) Hi Steve, good to hear from you again. Would you mind lokking into this: (URL) (15 years ago, 5-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) I'm gonna explain (and quit afterwards) why I hesitate adding new and old - what I call "MLCad" - colors to the LDConfig.ldr file: * The current LDConfig.ldr contains only colors you'll find in official LEGO Bricks (with two exceptions (...) (15 years ago, 6-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) OK, I'll update my programs to use this algoritm for colors not stated in ldconfig.ldr /Lars (15 years ago, 7-Dec-09, to lugnet.cad.dev.org.ldraw)
|
