Subject:
|
Re: ldconfig.ldr and dithered colors
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Sun, 6 Feb 2005 06:15:27 GMT
|
Viewed:
|
2623 times
|
| |
|
|
In lugnet.cad.dev, Lars C. Hassing wrote:
> How is a renderer expected to handle dithered colors not mentioned explicitly in ldconfig.ldr ?
>
> The "LDraw File Format" specification says:
> "Also, colours 256 through 511 are dithered. So if you want to combine colours J and K, figure your colour value as
> colour = (J * 16) + K + 256
> The complementary colour of J is used as the complementary colour of the dithered value.
> So you can control the edge colour (somewhat) by switching J and K."
>
> This is fine, but for LGEO colors L3P has always tried K,J if J,K wasn't in L2P_COLR.TAB,
> i.e. since 10,15 (431) is not defined, L3P tries 15,10 (506) and matches lg_mint.
>
> I see that ldconfig.ldr has different entries for 7,15 (383 Chrome_Silver) and 15,7 (503 Light_Gray)
> and 4,14 (334 Chrome_Gold) and 14,4 (484 Dark_Orange).
>
> But for e.g. 1,0 (272 Dark_Blue) there's no 0,1 (257),
> so what should color 257 be ?
> 272 or a blend of 0 and 1 ?
I'd say a blend of 0 and 1, basically just as if it's counterpart (272) wasn't
defined in the ldconfig
-Orion
|
|
Message is in Reply To:
 | | ldconfig.ldr and dithered colors
|
| How is a renderer expected to handle dithered colors not mentioned explicitly in ldconfig.ldr ? The "LDraw File Format" specification says: "Also, colours 256 through 511 are dithered. So if you want to combine colours J and K, figure your colour (...) (20 years ago, 6-Feb-05, to lugnet.cad.dev)
|
3 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
