|
|
 | | Re: Old Dithered Colors
|
| (...) Sorry, when I read your first message, I thought you meant MLCad would no longer support the predefined colors 256-511. Using derived values instead of literally dithering is just fine, I agree. Steve (18 years ago, 12-Jul-06, to lugnet.cad)
| | | | | Re: Old Dithered Colors
|
| (...) I agree with this, if you mean that the program should calculate the "average" color of the two dithered components. (And this is what LDView has done all along.) (...) I don't understand why you need to perform any color space conversion. If (...) (18 years ago, 12-Jul-06, to lugnet.cad)
| | | | | Re: Old Dithered Colors
|
| "Travis Cobbs" <tcobbs@REMOVE.halibut.com> schrieb im Newsbeitrag news:J2B0n8.4IB@lugnet.com... (...) That was what I was thinking of. I still will support the color codes as such, but I think that I will stop support for defining dithered colors. (...) (18 years ago, 12-Jul-06, to lugnet.cad)
| | | | | Re: Old Dithered Colors
|
| (...) I don't see the point in dithering any more either. It slows things down and was meant to simulate colours in the days before 24bit colour was ubiquitous. I would prefer you to just average the two colours (in RGB or CMY). Tim (18 years ago, 12-Jul-06, to lugnet.cad)
| | | | | Re: Old Dithered Colors
|
| (...) I definitely think MLCad should continue to recognize the color numbers. When I wrote LDView, I decided not to dither the colors, and just calculate the final color. I really think this is the best way to go (at least if the display is true (...) (18 years ago, 12-Jul-06, to lugnet.cad)
|
|
