 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Thorsten Froehlich" wrote:
> I am not able to find this in the web interface...
Because the web interface doesn't support povray.pre-beta.
To avoid the problem we're seeing here I asked Warp to repost the bug report
in povray.beta-test but he never did that so I had to refer to the message
in pre-beta.
Rune
--
3D images and anims, include files, tutorials and more:
Rune's World: http://rsj.mobilixnet.dk (updated June 26)
POV-Ray Users: http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk
Post a reply to this message
|
|
| |
| |
|
|
From: Thorsten Froehlich
Subject: Re: List of known bugs - any takers?
Date: 24 Oct 2001 15:44:10
Message: <3bd71a0a@news.povray.org>
|
|
|
| |
| |
|
|
In article <3bd70893@news.povray.org> , "Rune" <run### [at] mobilixnet dk>
wrote:
> Because the web interface doesn't support povray.pre-beta.
For which a web link is of course hopeless as the group is not public. Now
that I knew where to look for it, it was of course no problem to find it...
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Rune" <run### [at] mobilixnetdk> wrote in message
news:3bd58f42@news.povray.org...
<snip>
Hmm, no takers?
I would volunteer, but I suspect that this would be a case of optomism
triumphing over reality...
Would it be any help if I supplied an online perl-run db?
eg. fields for:
bug
beta version
type (doc/wrong output/crash/etc)
reported by
verified by
pov team confirmed
ref: (url to news message)
sample code (if applic)
fixed
fix version
?
This wouldn't duplicate the beta-test ng - it would only be for recording bugs
that had been acknowledged in the group...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Rune <run### [at] mobilixnetdk> wrote:
: To avoid the problem we're seeing here I asked Warp to repost the bug report
: in povray.beta-test but he never did that so I had to refer to the message
: in pre-beta.
I can post a formal bug report here if you want and it's necessary...
--
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Warp" wrote:
> I can post a formal bug report here if you
> want and it's necessary...
Part of the purpose of the list is that users don't keep reporting bugs that
are already known. If users should be able to see the bug report then it's
necessary to repost the bug report in povray.beta-test.
As to what *I* want, that's irrelevant as I don't manage the list anymore. I
hope someone will take over.
Rune
--
3D images and anims, include files, tutorials and more:
Rune's World: http://rsj.mobilixnet.dk (updated June 26)
POV-Ray Users: http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Tom Melly" wrote:
> Hmm, no takers?
Nope.
> I would volunteer, but I suspect that this would
> be a case of optomism triumphing over reality...
It's not very difficult really, if you have the time to read all the
messages in this group.
The list is practically just a list of references to messages posted in this
group and the binaries group.
> Would it be any help if I supplied an online perl-run db?
> This wouldn't duplicate the beta-test ng - it would only
> be for recording bugs that had been acknowledged in the
> group...
Well, I don't think that's what's needed. It won't be of any use if nobody
maintains the list in the first place, as it only adds additional work to
the maintaining job.
Rune
--
3D images and anims, include files, tutorials and more:
Rune's World: http://rsj.mobilixnet.dk (updated June 26)
POV-Ray Users: http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Rune" <run### [at] mobilixnetdk> wrote in message
news:3bd88cfc@news.povray.org...
>
> > Would it be any help if I supplied an online perl-run db?
>
> > This wouldn't duplicate the beta-test ng - it would only
> > be for recording bugs that had been acknowledged in the
> > group...
>
> Well, I don't think that's what's needed. It won't be of any use if nobody
> maintains the list in the first place, as it only adds additional work to
> the maintaining job.
>
IMHO I don't think it would add additional work - rather the opposite.
a) it would serve as a common reference point for people to check against to see
if a bug they'd found had already been reported (this group's signal to noise
ratio can be a problem in that respect)
b) anyone could add to the db, but the understanding would be that they should
only do so after confirming with this group that they'd found a bug
c) like a) but for the bug-fixers to see which bugs were outstanding
Anyway, I'll go ahead and do it and then the pov-team can take a look and see if
it looks like a useful resource if no one has any objections? If it's no good,
the only time wasted is my own....
Post a reply to this message
|
|
| |
| |
|
|
From: Thorsten Froehlich
Subject: Re: List of known bugs - any takers?
Date: 26 Oct 2001 06:33:45
Message: <3bd93c09@news.povray.org>
|
|
|
| |
| |
|
|
In article <3bd936bd$1@news.povray.org> , "Tom Melly" <tom### [at] tomandlucouk>
wrote:
> a) it would serve as a common reference point for people to check against to
> see if a bug they'd found had already been reported (this group's signal to
> noise ratio can be a problem in that respect)
>
> b) anyone could add to the db, but the understanding would be that they should
> only do so after confirming with this group that they'd found a bug
>
> c) like a) but for the bug-fixers to see which bugs were outstanding
>
> Anyway, I'll go ahead and do it and then the pov-team can take a look and see
> if it looks like a useful resource if no one has any objections? If it's no
> good, the only time wasted is my own....
This is just my own opinion, not speaking for the POV-Team:
The POV-Team already has a non-public* formal bug tracking system and is
aware of outstanding bugs once they find the way into our system (as our
time permits to enter that information there). I don't think anybody in the
team has the time to look at yet another tracking system and/or keep the
data consistent. A simple newsgroup message with a list is really
sufficient if it is up to date. If posted once a week every user should
really be able to read it before posting a bug report.
Thorsten
* If we would make it public we for sure would get lots of people
second-guessing why one or the other bug isn't fixed. Further, some bugs
are not related to POV-Ray directly but are internal issues that should be
changed sometime in the near or distant future...
____________________________________________________
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:3bd93c09@news.povray.org...
>
> This is just my own opinion, not speaking for the POV-Team:
>
> The POV-Team already has a non-public* formal bug tracking system and is
> aware of outstanding bugs once they find the way into our system (as our
> time permits to enter that information there). I don't think anybody in the
> team has the time to look at yet another tracking system and/or keep the
> data consistent. A simple newsgroup message with a list is really
> sufficient if it is up to date. If posted once a week every user should
> really be able to read it before posting a bug report.
>
Ahh! - I wrongly assumed that the posted bug list was the common reference for
the developers as well.
In that case, I withdraw my suggestion. Thanks for the info....
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Wasn't it Thorsten Froehlich who wrote:
>> Superellipsoid epsilon to big ?
>> http://news.povray.org/3b992a81@news.povray.org
>
>I cannot find anybody confirming this bug, maybe it got in this list by
>accident?
I can't find any previous confirmation, but a quick test shows that it
still does happen in 3.5b7 (Windows 98se. AMD K6-2 500. 128Mb.)
When the "radius" of the blob components is set very small, holes appear
in the blob surface.
--
Mike Williams
Gentleman of Leisure
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
