| | Re: [LDLite] Codes for new colors
|
| Lets see, I'll dig out my source here. In file stub.c, in the routine translate_color(), the color numbers 0-15, 17-23 and 25 are hard-coded to non-dithered colors. Colors 16 and 24 are of course "special" colors. Colors 25-32 inclusive are as yet (...) (26 years ago, 28-Oct-98, to lugnet.cad)
| | | | Re: [LDLite] Codes for new colors
|
| (...) What about colors 431, 495, and 382? They appear to be rendering as solid colors. (Note to self: colors 256, 273, 290, 307, 324, 341, 358, 375, 392, 409, 426, 443, 460, 477, 494, and 511 look solid because they are dithering a solid color with (...) (26 years ago, 28-Oct-98, to lugnet.cad)
| | | | Re: [LDLite] Codes for new colors
|
| Yep, I can confirm they render as as solid. I have no idea why, but I'll try to look into it. Personally I'd like to switch over to a name-based color specification, since I'm still not sure what color I should use for trans-flourescent-green. Then (...) (26 years ago, 28-Oct-98, to lugnet.cad)
| | | | Re: [LDLite] Codes for new colors
|
| (...) OK. Thanks. As long as I'm not crazy. Or losing my eyesight. BTW, does the currently-available version of LDLite poll for updates to the model-file? I'm playing around with this, launching LDLite and then changing the model-file, and I'm not (...) (26 years ago, 28-Oct-98, to lugnet.cad)
| | | | Re: [LDLite] Codes for new colors
|
| Version 1.1 should be doing this. You need to specify -p on the command line to enable polling. -gyug (...) (26 years ago, 29-Oct-98, to lugnet.cad)
| | | | Re: [LDLite] Codes for new colors
|
| oh, duh. Silly me. Thanks for the reminder. Yep, that works much better. Steve (...) (26 years ago, 29-Oct-98, to lugnet.cad)
| |