|
 |
"Darren New" <dne### [at] san rr com> wrote in message
news:470cf833$1@news.povray.org...
> Alain wrote:
>> You obviously miss a fundamental point: there is only ONE transform
>> matrix per object that contain the SUMATION of every single transforms
>> applyed to that object. There is no transform array, there never was any
>> such thing.
>
> I'm amazed at the number of people arguing
> "This is how the next one should be."
> "No, this is how the current one is."
> "But this is how the *next* one should be."
> "Don't you understand this is how the current one *is*?"
that's not how it is, it's more like this:
"This is how the next one should be."
"No, this is how the current one is, and there's absolutely no reason why
that particular part should change."
"But this is how the *next* one should be."
"You really don't understand why the current one is the way it is, do you?"
If you ask me, keeping an array of transformations makes it all needlessly
complicated. If you want such an array, define it yourself in SDL, there's
absolutely no need for it in the POV-core.
In my opinion, the main idea of the new SDL should be to seperate the
core-functionality from the user-definable functionality. At the very base
of the rendering-process, having an array of transformations is simply
ridiculous. If users want such an array, then I'm sure someone will write
an inc-file (or whatever) that makes this possible and even easy to do.
cu!
--
#macro G(b,e)b+(e-b)*C/50#end#macro _(b,e,k,l)#local C=0;#while(C<50)
sphere{G(b,e)+3*z.1pigment{rgb G(k,l)}finish{ambient 1}}#local C=C+1;
#end#end _(y-x,y,x,x+y)_(y,-x-y,x+y,y)_(-x-y,-y,y,y+z)_(-y,y,y+z,x+y)
_(0x+y.5+y/2x)_(0x-y.5+y/2x) // ZK http://www.povplace.com
Post a reply to this message
|
 |