I am not any form of expert on this or any subject for that matter. So,
please understand my naivete on this subject. I am worried that I may just


    Up to recently I have been a programmer, of 20 years experience in
non-related subjects, before my disability put a period on the end of my
career. As I read the quoted message, I began to think, as I would back
then. I wondered if the following was possible. I know the people here are
the true experts and will know the feasibility of my idea in an instant. I
hope they will correct me if wrong, just not too harshly...

    I would approach this problem by creating a global variable, an optional
arg to the command, or ini/inc file entry. So legacy POV programs
using/requiring the older form of the variable data is unaffected. This
would be because the default value will remain the original value. In
addition, those wishing a different one can just add the optional arg, set
the global, or make an ini/inc file entry.

    I do not know if this is a good idea or not. Nevertheless, hope it will
help. There may be another way to do it that I, do to my lack of knowledge
of POV, do not know...


"Ron Parker" <ron### [at] povrayorg> wrote in message
news:38d794a0$1@news.povray.org...
> On Tue, 21 Mar 2000 08:17:07 -0500, Greg M. Johnson wrote:
> >We have all discussed the issue many times without answering the
> >following question:
> >
> >How *hard* would it be to "fix" pov to eliminate the plateuas that exist
> >in the noise3d function?
>
> It's not a question of how hard it would be, it's a question of how many
> scene files it would break.
>
> --
> These are my opinions.  I do NOT speak for the POV-Team.
> The superpatch: http://www2.fwi.com/~parkerr/superpatch/
> My other stuff: http://www2.fwi.com/~parkerr/traces.html

Post a reply to this message