 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Could it be possible to present list of things (bugs?) which are noted
but won't be changed becouse of philosophy or limitations of current
level of POV-Ray ? Could be this list builded into doc ?
Personally I have set of stopped works based on such things and I
can't find answers from Team about them. Other people could find such
list usefull too.
ABX
--
#declare _=function(a,b,x){((a^2)+(b^2))^.5-x}#default {pigment{color rgb 1}}
union{plane{y,-3}plane{-x,-3}finish{reflection 1 ambient 0}}isosurface{ //ABX
function{_(x-2,y,1)|_((x+y)*.7,z,.1)|_((x+y+2)*.7,z,.1)|_(x/2+y*.8+1.5,z,.1)}
contained_by{box{<0,-3,-.1>,<3,0,.1>}}translate z*15finish{ambient 1}}//POV35
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Skiba <abx### [at] babilon org> wrote:
> Could it be possible to present list of things (bugs?) which are noted
> but won't be changed becouse of philosophy or limitations of current
> level of POV-Ray ? Could be this list builded into doc ?
Personally I think such a list would not be a good idea because out of ten
people who read it one will end up making assumptions and send suggestions
or complaints to the team. This would flood the team with (useless)
suggestions how to fix or change this and that from people who don't know
the usually very complex technical details -- I am not making this up, this
has already happened* (once) during the 3.5 public beta :-(
Thorsten
* I am talking about email, not any discussion in this group.
____________________________________________________
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Mon, 29 Oct 2001 11:04:27 +0100, "Thorsten Froehlich"
<tho### [at] trfde> wrote:
> Personally I think such a list would not be a good idea because out of ten
> people who read it one will end up making assumptions and send suggestions
> or complaints to the team. This would flood the team with (useless)
> suggestions how to fix or change this and that from people who don't know
> the usually very complex technical details.
I thought about list with note "no discussion about it, there are more
important things to do ;-)". This could stop some testers to send
"this still not works" after every beta version.
> I am not making this up, this
> has already happened* (once) during the 3.5 public beta :-(
If you have such experience you are probably right.
ABX
--
#declare _=function(a,b,x){((a^2)+(b^2))^.5-x}#default {pigment{color rgb 1}}
union{plane{y,-3}plane{-x,-3}finish{reflection 1 ambient 0}}isosurface{ //ABX
function{_(x-2,y,1)|_((x+y)*.7,z,.1)|_((x+y+2)*.7,z,.1)|_(x/2+y*.8+1.5,z,.1)}
contained_by{box{<0,-3,-.1>,<3,0,.1>}}translate z*15finish{ambient 1}}//POV35
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Skiba <abx### [at] babilonorg> wrote:
>> Personally I think such a list would not be a good idea because out of ten
>> people who read it one will end up making assumptions and send suggestions
>> or complaints to the team. This would flood the team with (useless)
>> suggestions how to fix or change this and that from people who don't know
>> the usually very complex technical details.
>
> I thought about list with note "no discussion about it, there are more
> important things to do ;-)".
If it would only work. Unfortunately no matter how one writes it, the more
information is given the more people will jump to conclusions. It seems it
is only getting worse because everybody who can "write" a 'hello world' in
Visual Basic thinks he/she is a programmer these days!
> This could stop some testers to send
> "this still not works" after every beta version.
Yes, this is a problem.
The team has said numerous times that only those bugs we lists as fixed in
the revision.txt/changes.txt have actually been fixed. Of course a few
people don't read those before posting again also we kindly ask them to read
the release notes and bug reports in this group first.
On the other hand, I wonder if a list of outstanding bugs would help those
people as they wouldn't read it either ;-)
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I think that it would be nice if at least some answer to people who post a
report or question or fix suggestion here would be given (one of three type
of answers: "Ok, we will fix that", "Ok, we will study this problem and see
if we can do something to it" or "No, this can't be fixed because ...").
There are some reports which seem to get no answer at all...
--
#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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3bdd427f@news.povray.org> , Warp <war### [at] tagpovrayorg> wrote:
> There are some reports which seem to get no answer at all...
As said in the welcome message of this groups:
"Do not expect a reply from the POV-Team."
Verifying bugs is something beta testers can and have to do, not the
POV-Team.
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 29 Oct 2001 06:50:24 -0500, Warp wrote:
> I think that it would be nice if at least some answer to people who post a
> report or question or fix suggestion here would be given (one of three type
> of answers: "Ok, we will fix that", "Ok, we will study this problem and see
> if we can do something to it" or "No, this can't be fixed because ...").
> There are some reports which seem to get no answer at all...
Not speaking for anyone else, but I only follow up to a report in this group
if I need further clarification or if I'm actively working on the problem and
have either a solution or more questions. Not every report has that status
with me; the ones that don't are still marked unread in my newsreader and I'll
get to them eventually.
--
#macro R(P)z+_(P)_(P)_(P+1)_(P+1)+z#end#macro Q(C,T)bicubic_patch{type 1u_steps
6v_steps 6R(1)R(3)R(5)R(7)pigment{rgb z}}#end#macro _(Y)#local X=asc(substr(C,Y
,1))-65;<T+mod(X,4)div(X,4)9>-2#end#macro O(T)Q("ABEFUQWS",T)Q("WSXTLOJN",T)#
end O(0)O(3)Q("JNKLCGCD",0)light_source{x 1}// ron### [at] povrayorg
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich <tho### [at] trfde> wrote:
:> There are some reports which seem to get no answer at all...
: As said in the welcome message of this groups:
: "Do not expect a reply from the POV-Team."
I know. I just said what would be *nice*... :)
--
#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
|
|
| |
| |
|
|
|
|
| |
|
|
