|
![](/i/fill.gif) |
Wasn't it Bob H. who wrote:
>"Mike Williams" <mik### [at] nospam please> wrote in message
>news:R4lTREAhsz$7Ewc3@econym.demon.co.uk...
>>
>> #include "colors"
>> //#declare MyColour = White - Gray25;
>> //#declare MyColour = 1 - Gray25;
>> #declare MyColour = rgb 1 - Gray25;
>>
>> #debug str(MyColour.red,0,2)
>> #debug ", "
>> #debug str(MyColour.green,0,2)
>> #debug ", "
>> #debug str(MyColour.blue,0,2)
>> #debug ", "
>> #debug str(MyColour.filter,0,2)
>> #debug ", "
>> #debug str(MyColour.transmit,0,2)
>> #debug "\n"
>>
>>
>> It could be argued that "rgb" should force the filter and transmit
>> values to zero, rather than just display the warning and accept non-zero
>> filters and/or transmits. (You did notice that you were getting the
>> warning "Suspicious expression after rgb.", didn't you?)
>
>Wait a minute. What's rgb 1 doing becoming rgbft 1 anyway.
It doesn't. If you try "#declare MyColour = rgb 1" in the above code
you'll see it becomes <1,1,1,0,0>.
--
Mike Williams
Gentleman of Leisure
Post a reply to this message
|
![](/i/fill.gif) |