|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
For some time now I have been wondering about the meaning of:
Parse warning: Suspicious expression after rgb.
There is no reference to any file in which this may happen, nor to the
suspicious place. I have been browsing different potential issues
without finding anything /suspicious/.
Any smart idea?
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 02/01/2013 13:02, Thomas de Groot nous fit lire :
> For some time now I have been wondering about the meaning of:
>
> Parse warning: Suspicious expression after rgb.
>
> There is no reference to any file in which this may happen, nor to the
> suspicious place. I have been browsing different potential issues
> without finding anything /suspicious/.
>
> Any smart idea?
Code analysis: warning due to number of terms in expression not equal to 3.
Lack of file location means that Token.FileHandle is NULL.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 01/02/2013 07:02 AM, Thomas de Groot wrote:
> For some time now I have been wondering about the meaning of:
>
> Parse warning: Suspicious expression after rgb.
>
> There is no reference to any file in which this may happen, nor to the
> suspicious place. I have been browsing different potential issues
> without finding anything /suspicious/.
>
> Any smart idea?
>
> Thomas
seen this before as well, iirc: look for pigment statements that have
rgb followed a predefined color like Yellow ... effectively it's seeing
it as pigment { rgb rgb <1,1,0> }
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> For some time now I have been wondering about the meaning of:
>
> Parse warning: Suspicious expression after rgb.
That warning is the one I most see... due to my tendency to mix
colors by arithmetic operations (i.e.: Red*.5+Yellow*.3). I learned to
just ignore it... ;)
--
Jaime
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 01/02/2013 09:16 AM, Jaime Vives Piqueres wrote:
>> For some time now I have been wondering about the meaning of:
>>
>> Parse warning: Suspicious expression after rgb.
>
> That warning is the one I most see... due to my tendency to mix
> colors by arithmetic operations (i.e.: Red*.5+Yellow*.3). I learned to
> just ignore it... ;)
>
> --
> Jaime
LOL that's where I'd seen that before, thanks for the nudge ... perhaps
my other recollection was incorrect then
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2-1-2013 15:16, Jaime Vives Piqueres wrote:
>> For some time now I have been wondering about the meaning of:
>>
>> Parse warning: Suspicious expression after rgb.
>
> That warning is the one I most see... due to my tendency to mix
> colors by arithmetic operations (i.e.: Red*.5+Yellow*.3). I learned to
> just ignore it... ;)
I also do that a lot (mixing and... ignoring) ;-)
I just got curious because sometimes it seems not to make sense,
everything loud an clear, so to speak, but I probably have some hidden
things I overlook in the process.
Thanks all for the clarification.
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Whenever I see that warning, I almost automatically go to section 3.2.1.5.5
"Common Color Pitfalls" in the docs, to 'refresh' my memory of the odd behavior
of dot operators re: colors. If some insight there doesn't solve it, then I
usually ignore it.
BTW, another irritation for me is seeing the warning about 'no pigment type
given' for an object when it's in a lightgroup. That *always* seems to happen
(in v3.6.2), for no apparent reason. Again, I just ignore it.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thomas de Groot <tho### [at] degrootorg> wrote:
> On 2-1-2013 15:16, Jaime Vives Piqueres wrote:
> >> For some time now I have been wondering about the meaning of:
> >>
> >> Parse warning: Suspicious expression after rgb.
> >
> > That warning is the one I most see... due to my tendency to mix
> > colors by arithmetic operations (i.e.: Red*.5+Yellow*.3). I learned to
> > just ignore it... ;)
>
> I also do that a lot (mixing and... ignoring) ;-)
>
> I just got curious because sometimes it seems not to make sense,
> everything loud an clear, so to speak, but I probably have some hidden
> things I overlook in the process.
>
> Thanks all for the clarification.
>
> Thomas
I'm not sure completelly but I see his warning often when I add a forth or fifth
component to a color vector (e.g. something like this: color Red +
<0,0,0,0.5,0.5>) to get filtered or general transmittance. Mainly within color
maps and the like.
Best regards,
Michael
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"MichaelJF" <mi-### [at] t-onlinede> wrote:
> Thomas de Groot <tho### [at] degrootorg> wrote:
> > On 2-1-2013 15:16, Jaime Vives Piqueres wrote:
> > >> For some time now I have been wondering about the meaning of:
> > >>
> > >> Parse warning: Suspicious expression after rgb.
> > >
> > > That warning is the one I most see... due to my tendency to mix
> > > colors by arithmetic operations (i.e.: Red*.5+Yellow*.3). I learned to
> > > just ignore it... ;)
> >
> > I also do that a lot (mixing and... ignoring) ;-)
> >
> > I just got curious because sometimes it seems not to make sense,
> > everything loud an clear, so to speak, but I probably have some hidden
> > things I overlook in the process.
> >
> > Thanks all for the clarification.
> >
> > Thomas
>
> I'm not sure completelly but I see his warning often when I add a forth or fifth
> component to a color vector (e.g. something like this: color Red +
> <0,0,0,0.5,0.5>) to get filtered or general transmittance. Mainly within color
> maps and the like.
>
> Best regards,
> Michael
My solution is like Kenneth's: ignore the warning.
Michael
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |