 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I am using version 3.6.1 (g++ 3.4.1 @ i686-pc-linux-gnu)
Op Fri, 13 Nov 2009 21:46:31 +0100, schreef clipka:
> Brickman Brick schrieb:
>> Hello,
>>
>> I made a cut-down version and posted it in povray.binaries.scene-files.
>> Unfortunately I can't reproduce the bug at the moment. But I you want
>> to have a look at it, it is there.
>
> Oops - something I should have asked earlier: What version of POV-Ray
> are you using?
--
brickcentral.livejournal.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Brickman Brick schrieb:
> Hello,
>
> I made a cut-down version and posted it in povray.binaries.scene-files.
> Unfortunately I can't reproduce the bug at the moment. But I you want to
> have a look at it, it is there.
I notice that in the code you sum up the total track length; did you
compare it between "good" and "wrong" case? This might give a hint
whether the #case statement is really cut short, or whether the
computatons give wrong results.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi,
thanks for the help. Maybe this will lead me to the exact spot of the
error. I know now that the #case statement has not been cut short, but
the wrong computation must be somewhere in the code that has been called
by the #case statement.
I am also going to try if the texture macro causes the error. As soon as
I am able to reproduce the bug again.
Op Fri, 13 Nov 2009 22:59:40 +0100, schreef clipka:
> I notice that in the code you sum up the total track length; did you
> compare it between "good" and "wrong" case? This might give a hint
> whether the #case statement is really cut short, or whether the
> computatons give wrong results.
--
brickcentral.livejournal.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
