 | | Re: Custom Color question/request —Joel Hoornbeek
|
| | | (...) Now that I've used it a bit more, another question comes up. I just defined some new colors that correspond to the new gray colors, and tried to render the file in LPub. However, the bricks that I had assigned my new colors to all came out as (...) (21 years ago, 24-Jan-04, to lugnet.cad)
|
| | | |
| | | | | Re: Custom Color question/request —Travis Cobbs
|
| | | | (...) L3P doesn't support the type of custom colors created with the define button. When you use a custom color in MLCAD, it uses an extended color number that defines the actual color used. This extended color number format originated with ldlite (...) (21 years ago, 24-Jan-04, to lugnet.cad)
|
| | | | |
| | | | | | Re: Custom Color question/request —Joel Hoornbeek
|
| | | | | (...) Thanks for all of the information, Travis. It does sound like I'll be better off with un-named colors that render properly instead of named colors that are all the same. :) -Joel (21 years ago, 25-Jan-04, to lugnet.cad)
|
| | | | | |
| | | | | | Re: Custom Color question/request —Willy Tschager
|
| | | | (...) a workaround for this problem is assigning a color number supported by L3P (256-511) plus redefining the color in an .inc file by placing it between the BUMP and AMB/DIF statement in POV w. (21 years ago, 27-Jan-04, to lugnet.cad)
|
| | | | |
