POV-Ray : Newsgroups : povray.general : Color Passing in #macro Server Time
10 Aug 2024 21:01:43 EDT (-0400)
  Color Passing in #macro (Message 7 to 16 of 16)  
<<< Previous 6 Messages Goto Initial 10 Messages
From: mr art
Subject: Re: more data
Date: 26 Nov 1999 14:22:52
Message: <383EDDEB.174731B4@gci.net>
Try this for simplest code :
// #declare CapColor= <1,0,0,0,0>;
   #declare CapColor= color <1,0,0,0,0>;
#warning "Vector <" 	#warning str(CapColor.red     ,0,4)
#warning ", "		#warning str(CapColor.green   ,0,4)
#warning ", "		#warning str(CapColor.blue    ,0,4)
#warning ", "		#warning str(CapColor.filter  ,0,4)
#warning ", "		#warning str(CapColor.transmit,0,4)
#warning "> "
sphere{0,0 pigment{color 0}}// keeps the error messages away

uncomment one or the other of the #declare statements.
#declare CapColor= color <1,0,0,0,0>; gives correct results
#declare CapColor= <1,0,0,0,0>; doesn't

So the problem seems to be not in the #macro stuff at all
but in the assignment process.

"mr.art" wrote:
> 
> Here is more data to ponder:
> #declare CapColor=<1,1,0,0>; outside the macro becomes <1,1,0,0> inside
> But
> #declare CapColor=<1,1,0,0,0>; becomes <0,1.875,0,1.875,0> inside


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: more data
Date: 26 Nov 1999 16:41:01
Message: <383efe6d@news.povray.org>
In article <383EDDEB.174731B4@gci.net> , "mr.art" <mr.### [at] gcinet> wrote:

> So the problem seems to be not in the #macro stuff at all
> but in the assignment process.

Yes, I can now verify your problem. It is a bug in the source code. A
detailed bug report has been posted to povray.bugreports.


     Thorsten


____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org


Post a reply to this message

From: mr art
Subject: Re: more data
Date: 26 Nov 1999 17:31:33
Message: <383F0A25.7E61D666@gci.net>
Thank you. I know that the easy workaround
is to use the keyword color in front of the vector.
But if someone had tried to 5d vectors for another
use, it could mess them up some. So, once again,
thank you.

Mr. Art

Thorsten Froehlich wrote:
> 
> In article <383EDDEB.174731B4@gci.net> , "mr.art" <mr.### [at] gcinet> wrote:
> 
> > So the problem seems to be not in the #macro stuff at all
> > but in the assignment process.
> 
> Yes, I can now verify your problem. It is a bug in the source code. A
> detailed bug report has been posted to povray.bugreports.
> 
>      Thorsten
> 
> ____________________________________________________
> Thorsten Froehlich
> e-mail: mac### [at] povrayorg
> 
> I am a member of the POV-Ray Team.
> Visit POV-Ray on the web: http://mac.povray.org


Post a reply to this message

From: Alan Kong
Subject: Re: more data
Date: 26 Nov 1999 18:23:16
Message: <5f5u3ssmp8f370e8qi7to6rsl0ua1u5ff1@4ax.com>
On Fri, 26 Nov 1999 15:40:53 -0600, "Thorsten Froehlich"
<tho### [at] trfde> wrote:

>Yes, I can now verify your problem. It is a bug in the source code. A
>detailed bug report has been posted to povray.bugreports.

  Thank you for posting the fix, Thorsten.

-- 
Alan - ako### [at] povrayorg - a k o n g <at> p o v r a y <dot> o r g
http://www.povray.org - Home of the Persistence of Vision Ray Tracer


Post a reply to this message

From: Chris Colefax
Subject: Re: Color Passing in #macro
Date: 26 Nov 1999 20:41:51
Message: <383f36df@news.povray.org>
mr.art <mr.### [at] gcinet> wrote:
> I just ran into something strange. While trying to
> pass a color vector through a macro, the color changed!
> The code is simple
[snip]
> If I #declare CapColor= a three or four component vector, it works
fine.
> But as a five component vector something doesn't work so well.
> Can anyone give some insight on this?

I think that second-last sentence is the clue: you don't actually want a
5-component vector, you want a colour.  Therefore, if you declare your
CapColor as a colour variable, eg: #declare CapColor = rgbft <1, 0, 0,
0, 0>; you should find that everything works as expected.


Post a reply to this message

From: Chris Colefax
Subject: Re: Color Passing in #macro
Date: 26 Nov 1999 20:41:54
Message: <383f36e2@news.povray.org>
Nieminen Juha <war### [at] punarastascstutfi> wrote:
>   It certainly looks like a bug. I don't know of any way of printing
the
> values of the vector when it has five components so I can't see what's
> happening. There seems to be no way to access the 5th component of a
vector
> and #write doesn't work for 5-dimensional vectors for some strange
reason.
>   5-dimensional vectors are obviously handled differently from 4 or
less
> dimensinal vectors, and perhaps the bug is related to that.

If the variable you want to pass is declared as a colour then everything
behaves as expected.  Taking into account other seemingly 'strange'
behaviour (eg. what happens when you specify checker colours without
commas, or try certain colour arithmetic) I don't think I'd classify
this as a bug.  Declaring a variable as a colour (using the color
prefix, or rgbft, etc.) also allows you to correctly access the filter
and transmit components using dot notation (although colours are not
supported by the #write function).


Post a reply to this message

From: Nieminen Juha
Subject: Re: Color Passing in #macro
Date: 29 Nov 1999 10:11:23
Message: <3842979b@news.povray.org>
Does this mean that when povray expects a vector and it finds a 5-dimensional
one, it promotes it to a 4-dimensional vector?

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/


Post a reply to this message

From: mr art
Subject: Re: Color Passing in #macro
Date: 29 Nov 1999 11:42:04
Message: <3842ACC3.D70701F8@gci.net>
Well,
#declare Test=<0,0,0,0,0>;
#declare Test=<0,0,0,0>;
generates: error: Attempted to redefine colour identifier as 4d-vector
identifier.

But,
#declare Test=<0,0,0,0,0>;
#declare TestPig=pigment{rgb Test}
generates no error. My assumption is it discards what it doesn't need.
Nieminen Juha wrote:
> 
>   Does this mean that when povray expects a vector and it finds a 5-dimensional
> one, it promotes it to a 4-dimensional vector?
> 
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: Color Passing in #macro
Date: 29 Nov 1999 19:46:48
Message: <38431e78@news.povray.org>
In article <3842979b@news.povray.org> , Nieminen Juha 
<war### [at] punarastascstutfi>  wrote:

>   Does this mean that when povray expects a vector and it finds a
5-dimensional
> one, it promotes it to a 4-dimensional vector?

No, it tries to use memcpy to convert an array of doubles to an array of
floats ... look at the report posted in povray.bugreports and the source of
this strange error will be obvious. Fortunately it doesn't copy more bytes,
but less!


    Thorsten


____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: Color Passing in #macro
Date: 29 Nov 1999 19:49:43
Message: <38431f27@news.povray.org>
In article <3842ACC3.D70701F8@gci.net> , "mr.art" <mr.### [at] gcinet> wrote:

> #declare Test=<0,0,0,0,0>;
> #declare TestPig=pigment{rgb Test}
> generates no error. My assumption is it discards what it doesn't need.

Nope, the error is very obsure from a non-programmer perspective.
In short it copies only some parts of the vector.


    Thorsten


____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org


Post a reply to this message

<<< Previous 6 Messages Goto Initial 10 Messages

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.