 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Here are the known and confirmed bugs as per today. Corrections to the list
are still very welcome.
18077 Blob problem
http://news.povray.org/povray.beta-test/18087/
18089 Blob : Toward a solution
http://news.povray.org/povray.beta-test/18089/
18094 Superellipsoid epsilon to big ?
http://news.povray.org/povray.beta-test/18094/
18105 Additional (?) blob bug
http://news.povray.org/povray.beta-test/18105/
18391 hf_gray_16 + png creates wrong output image
http://news.povray.org/povray.beta-test/18391/
18456 Blob rendering error
http://news.povray.org/povray.beta-test/18456/
18522 Small window title bug
(Title switches back to "POV-Ray for Windows" after minimize or restore. )
http://news.povray.org/povray.beta-test/18522/
18529 16-bit PGM pigment and height field problems
http://news.povray.org/povray.beta-test/18529/
18535 Blend map crash
http://news.povray.org/povray.beta-test/18535/
18565 Radiosity with recursion > 1
(With recursion_limit > 1 clear axis aligned bands appear on the surfaces.)
http://news.povray.org/povray.beta-test/18565/
18577 Rendering animation (MS Windows)
(Message that indicates the frame to be render is displayed AFTER the
rendering.)
http://news.povray.org/povray.beta-test/18577/
18638 Stop during mosaic: crash
http://news.povray.org/povray.beta-test/18638/
18650 sin(X)^sin(X) -> crash!
http://news.povray.org/povray.beta-test/18650/
18672 Bug with parse_string
http://news.povray.org/povray.beta-test/18672/
18740 Spline bug
(The spline path is all wrong when certain time values are used.)
http://news.povray.org/povray.beta-test/18740/
18746 Radiosity crash when user stops render during pretrace.
http://news.povray.org/povray.beta-test/18746/
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] mobilixnet dk> wrote in message
news:3bb4956d@news.povray.org...
>
> 18391 hf_gray_16 + png creates wrong output image
> http://news.povray.org/povray.beta-test/18391/
Just found that hf_gray_16 (on) won't allow a render to proceed. That bug
mentioned was only about TGA file output being okay but not for PNG and with
the Beta 2. I get the message:
File Init Error: Cannot open output file.
whether png or tga is specified.
Intel opt. Beta 4, WinMe, PIII, 512MB
Bob H.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Just found a message by Bonsai here from the 24th saying the same thing I
just did about File Init Error. Ron suggests it would be fixed in Beta 5.
Bob H.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 28 Sep 2001 22:04:40 -0500, Bob H. wrote:
>Just found a message by Bonsai here from the 24th saying the same thing I
>just did about File Init Error. Ron suggests it would be fixed in Beta 5.
Or some future beta. One never knows; I might check it in just after Chris
starts building the beta.
--
#macro R(L P)sphere{L __}cylinder{L P __}#end#macro P(_1)union{R(z+_ z)R(-z _-z)
R(_-z*3_+z)torus{1__ clipped_by{plane{_ 0}}}translate z+_1}#end#macro S(_)9-(_1-
_)*(_1-_)#end#macro Z(_1 _ __)union{P(_)P(-_)R(y-z-1_)translate.1*_1-y*8pigment{
rgb<S(7)S(5)S(3)>}}#if(_1)Z(_1-__,_,__)#end#end Z(10x*-2,.2)camera{rotate x*90}
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
You forgot to mention the *sphere_sweep with radiosity bug*
--
Jonathan
"Rune" <run### [at] mobilixnetdk> ha scritto nel messaggio
news:3bb4956d@news.povray.org...
> Here are the known and confirmed bugs as per today. Corrections to the
list
> are still very welcome.
>
> 18077 Blob problem
> http://news.povray.org/povray.beta-test/18087/
>
> 18089 Blob : Toward a solution
> http://news.povray.org/povray.beta-test/18089/
>
> 18094 Superellipsoid epsilon to big ?
> http://news.povray.org/povray.beta-test/18094/
>
> 18105 Additional (?) blob bug
> http://news.povray.org/povray.beta-test/18105/
>
> 18391 hf_gray_16 + png creates wrong output image
> http://news.povray.org/povray.beta-test/18391/
>
> 18456 Blob rendering error
> http://news.povray.org/povray.beta-test/18456/
>
> 18522 Small window title bug
> (Title switches back to "POV-Ray for Windows" after minimize or restore. )
> http://news.povray.org/povray.beta-test/18522/
>
> 18529 16-bit PGM pigment and height field problems
> http://news.povray.org/povray.beta-test/18529/
>
> 18535 Blend map crash
> http://news.povray.org/povray.beta-test/18535/
>
> 18565 Radiosity with recursion > 1
> (With recursion_limit > 1 clear axis aligned bands appear on the
surfaces.)
> http://news.povray.org/povray.beta-test/18565/
>
> 18577 Rendering animation (MS Windows)
> (Message that indicates the frame to be render is displayed AFTER the
> rendering.)
> http://news.povray.org/povray.beta-test/18577/
>
> 18638 Stop during mosaic: crash
> http://news.povray.org/povray.beta-test/18638/
>
> 18650 sin(X)^sin(X) -> crash!
> http://news.povray.org/povray.beta-test/18650/
>
> 18672 Bug with parse_string
> http://news.povray.org/povray.beta-test/18672/
>
> 18740 Spline bug
> (The spline path is all wrong when certain time values are used.)
> http://news.povray.org/povray.beta-test/18740/
>
> 18746 Radiosity crash when user stops render during pretrace.
> http://news.povray.org/povray.beta-test/18746/
>
> 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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 28 Sep 2001 17:15:53 +0200, "Rune"
<run### [at] mobilixnetdk> wrote:
> Here are the known and confirmed bugs as per today. Corrections to the list
> are still very welcome.
Perhaps there is a reason but you attached only one my post.
Here are other not finished with explanation or "will be fixed"
Crash after constant function
http://news.povray.org/povray.beta-test/18496/
Bug with intersection stack (I gave solution)
http://news.povray.org/povray.beta-test/18696/
#if inside #if (but Nathan said - no solution anywhere :-( )
http://news.povray.org/povray.beta-test/18701/
Another string bug (or even two)
http://news.povray.org/povray.beta-test/18706/
Old accuracy bug - perhaps with no chance to fix
http://news.povray.org/povray.beta-test/18702/
There is also something new from me
Select within select
http://news.povray.org/povray.beta-test/18823/
I answered for your request for help
http://news.povray.org/povray.beta-test/18618/
Have you readed this? Was this helpful ? Should I continue ?
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"W³odzimierz ABX Skiba" wrote:
> Perhaps there is a reason but you attached only
> one my post. Here are other not finished with
> explanation or "will be fixed"
Note:
Only confirmed bugs can get on the list.
You couldn't know this, but for the future, please specify messages this
way:
http://news.povray.org/Xns9115B92CF7D8ACQ@204.213.191.226
(The part after http://news.povray.org/ is the message ID.)
> Crash after constant function
> http://news.povray.org/povray.beta-test/18496/
I'll add this.
> Bug with intersection stack (I gave solution)
> http://news.povray.org/povray.beta-test/18696/
I'll add it.
> #if inside #if (but Nathan said - no solution anywhere :-( )
> http://news.povray.org/povray.beta-test/18701/
That's not a bug but a limitation.
> Another string bug (or even two)
> http://news.povray.org/povray.beta-test/18706/
I'll add "Crash with long strings, ignore documentation bug report"
> Old accuracy bug - perhaps with no chance to fix
> http://news.povray.org/povray.beta-test/18702/
This bug doesn't seem to have been confirmed.
> Select within select
> http://news.povray.org/povray.beta-test/18823/
This hasn't been confirmed properly.
> I answered for your request for help
> http://news.povray.org/povray.beta-test/18618/
> Have you readed this? Was this helpful ? Should I continue ?
Yes. Yes. Yes. (Sorry I didn't answer before to that.)
Rune
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Mon, 1 Oct 2001 20:28:47 +0200, "Rune"
<run### [at] mobilixnetdk> wrote:
>Only confirmed bugs can get on the list.
ok.
> You couldn't know this, but for the future, please specify messages this
> way:
> http://news.povray.org/Xns9115B92CF7D8ACQ@204.213.191.226
> (The part after http://news.povray.org/ is the message ID.)
where on the www interface I can find it that way ?
> > Crash after constant function
> > http://news.povray.org/povray.beta-test/18496/
>
> I'll add this.
is seems it's gone for beta 6
> > Bug with intersection stack (I gave solution)
> > http://news.povray.org/povray.beta-test/18696/
>
> I'll add it.
it still present for beta 6
> > #if inside #if (but Nathan said - no solution anywhere :-( )
> > http://news.povray.org/povray.beta-test/18701/
>
> That's not a bug but a limitation.
than I must wait for sources :-(
> > Another string bug (or even two)
> > http://news.povray.org/povray.beta-test/18706/
>
> I'll add "Crash with long strings, ignore documentation bug report"
is seems it's gone for beta 6
> > Old accuracy bug - perhaps with no chance to fix
> > http://news.povray.org/povray.beta-test/18702/
>
> This bug doesn't seem to have been confirmed.
can anybody confirm this ?
I can confirm that it still present for beta 6
> > Select within select
> > http://news.povray.org/povray.beta-test/18823/
>
> This hasn't been confirmed properly.
yes, wrong noise generator
> > I answered for your request for help
> > http://news.povray.org/povray.beta-test/18618/
> > Have you readed this? Was this helpful ? Should I continue ?
>
> Yes. Yes. Yes. (Sorry I didn't answer before to that.)
ok, I see it is still not finished for beta 6 therefore I'll start
with it.
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <ahn7ttc31av05805lom27csqk778mpdvvl@4ax.com> , W„odzimierz ABX
Skiba <abx### [at] babilonorg> wrote:
>> http://news.povray.org/Xns9115B92CF7D8ACQ@204.213.191.226
>> (The part after http://news.povray.org/ is the message ID.)
>
> where on the www interface I can find it that way ?
Just _follow_ the link, at is all you need to do 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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Mon, 22 Oct 2001 12:46:59 +0200, "Thorsten Froehlich"
<tho### [at] trfde> wrote:
> Just _follow_ the link, at is all you need to do to find it.
perhaps there is some limitation in my English but I not asked how use
links but how generate link with message ID having opened message via
www interface
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <q338tt4tlomhlieng38togpei5t3i8phf4@4ax.com> , W„odzimierz ABX
Skiba <abx### [at] babilonorg> wrote:
>> Just _follow_ the link, at is all you need to do to find it.
>
> perhaps there is some limitation in my English but I not asked how use
> links but how generate link with message ID having opened message via
> www interface
No, this is a mistake on my part. I misunderstood the question.
The short answer is: You can't.
The long answer is: You can build it on your own, but you need a newsreader
that can show you the message header. Then just take the message ID header
field and combine it with the link to the main newsgroup web interface page.
While the resulting link is not compatible with old browsers (because the
URL isn't encoded properly), it will work with all more recent browsers.
Alternatively you can use Netscape to get a link in the same format with a
properly encoded URL. You just change the news:// Netscape puts in front to
a http:// and you are all set. The web interface does not care if the URL
is encoded properly or not.
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"W³odzimierz ABX Skiba" wrote:
> ok, I see it is still not finished for beta 6
> therefore I'll start with it.
Thank you! It's very appreciated.
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Mon, 22 Oct 2001 20:05:24 +0200, "Rune" <run### [at] mobilixnetdk> wrote:
> Thank you! It's very appreciated.
this macro is not on the list but I think it could be usefull
(and that's why I talked so much about declaring arrays
and pointing to elements with loops - this macro could
be veeery short with it)
// Array - an array to be resized
// Dimension - number of dimension to be resized
// NewSize - new number of entries for Dimension of Array
#macro Resize_Multi_Array(Array, Dimension, NewSize)
#if((Dimension>0)&(dimensions(Array)>=Dimension)&(int(Dimension)=Dimension))
#if(dimensions(Array)!=1)
#switch(dimensions(Array))
#case(2)
#local NewArray=array
[(Dimension!=1?dimension_size(Array,1):NewSize)]
[(Dimension!=2?dimension_size(Array,2):NewSize)]
#local Max1 =
min(dimension_size(NewArray,1),dimension_size(Array,1));
#break
#case(3)
#local NewArray=array
[(Dimension!=1?dimension_size(Array,1):NewSize)]
[(Dimension!=2?dimension_size(Array,2):NewSize)]
[(Dimension!=3?dimension_size(Array,3):NewSize)]
#break
#case(4)
#local NewArray=array
[(Dimension!=1?dimension_size(Array,1):NewSize)]
[(Dimension!=2?dimension_size(Array,2):NewSize)]
[(Dimension!=3?dimension_size(Array,3):NewSize)]
[(Dimension!=4?dimension_size(Array,4):NewSize)]
#break
#case(5)
#local NewArray=array
[(Dimension!=1?dimension_size(Array,1):NewSize)]
[(Dimension!=2?dimension_size(Array,2):NewSize)]
[(Dimension!=3?dimension_size(Array,3):NewSize)]
[(Dimension!=4?dimension_size(Array,4):NewSize)]
[(Dimension!=5?dimension_size(Array,5):NewSize)]
#break
#else
#error "Wrong Dimension argument in Resize_Multi_Array macro"
#end
#local Max=array[dimensions(Array)]
#local C=0;
#while (C<dimensions(Array))
#local
Max[C]=min(dimension_size(NewArray,C+1),dimension_size(Array,C+1));
#local C=C+1;
#end
#local C=Max
#switch(dimensions(Array))
#case(2)
#local C[0]=0;
#while (C[0]<Max[0])
#local C[1]=0;
#while(C[1]<Max[1])
#ifdef(Array[C[0]][C[1]])
#local NewArray[C[0]][C[1]] = Array[C[0]][C[1]];
#end
#local C[1] = C[1] + 1;
#end
#local C[0] = C[0] + 1;
#end
#break
#case(3)
#local C[0]=0;
#while (C[0]<Max[0])
#local C[1]=0;
#while(C[1]<Max[1])
#local C[2]=0;
#while(C[2]<Max[2])
#ifdef(Array[C[0]][C[1]][C[2]])
#local NewArray[C[0]][C[1]][C[2]] =
Array[C[0]][C[1]][C[2]];
#end
#local C[2] = C[2] + 1;
#end
#local C[1] = C[1] + 1;
#end
#local C[0] = C[0] + 1;
#end
#break
#case(4)
#local C[0]=0;
#while (C[0]<Max[0])
#local C[1]=0;
#while(C[1]<Max[1])
#local C[2]=0;
#while(C[2]<Max[2])
#local C[3]=0;
#while(C[3]<Max[3])
#ifdef(Array[C[0]][C[1]][C[2]][C[3]])
#local NewArray[C[0]][C[1]][C[2]][C[3]] =
Array[C[0]][C[1]][C[2]][C[3]];
#end
#local C[3] = C[3] + 1;
#end
#local C[2] = C[2] + 1;
#end
#local C[1] = C[1] + 1;
#end
#local C[0] = C[0] + 1;
#end
#break
#case(5)
#local C[0]=0;
#while (C[0]<Max[0])
#local C[1]=0;
#while(C[1]<Max[1])
#local C[2]=0;
#while(C[2]<Max[2])
#local C[3]=0;
#while(C[3]<Max[3])
#local C[4]=0;
#while(C[4]<Max[4])
#ifdef(Array[C[0]][C[1]][C[2]][C[3]][C[4]])
#local
NewArray[C[0]][C[1]][C[2]][C[3]][C[4]] = Array[C[0]][C[1]][C[2]][C[3]][C[4]];
#end
#local C[4] = C[4] + 1;
#end
#local C[3] = C[3] + 1;
#end
#local C[2] = C[2] + 1;
#end
#local C[1] = C[1] + 1;
#end
#local C[0] = C[0] + 1;
#end
#break
#else
#error "Wrong Dimension argument in Resize_Multi_Array macro"
#end
#declare Array = NewArray
#else
Resize_Array(Array,NewSize)
#end
#else
#error "Wrong Dimension argument in Resize_Multi_Array macro"
#end
#end
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"W³odzimierz ABX Skiba" wrote:
> this macro is not on the list but I think it could be usefull
Hmm, I don't know, so I'd like to hear the opinions of others. Is this macro
useful enough for inclusion?
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Why don't you allow the array to be one-dimensional? I know that there are
other macros for one-dimensional arrays, but it's trivial to add and it
would make this macro truly general-purpose.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Rune wrote:
> "Włodzimierz ABX Skiba" wrote:
>
>>this macro is not on the list but I think it could be usefull
>>
>
> Hmm, I don't know, so I'd like to hear the opinions of others. Is this macro
> useful enough for inclusion?
Yes imho
Philippe
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Mon, 29 Oct 2001 18:19:33 +0100, "Rune"
<run### [at] mobilixnetdk> wrote:
> "W?odzimierz ABX Skiba" wrote:
> > this macro is not on the list but I think it could be usefull
>
> Hmm, I don't know, so I'd like to hear the opinions of others. Is this macro
> useful enough for inclusion?
I've designed this macro becouse I planned to write Append_To_Array
and Append_Array_To_Array macros working multidimensional.
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Mon, 29 Oct 2001 13:12:59 -0500, "Anders K." <and### [at] f2scom>
wrote:
> Why don't you allow the array to be one-dimensional? I know that there are
> other macros for one-dimensional arrays, but it's trivial to add and it
> would make this macro truly general-purpose.
perhaps you missed this but I don't allow, I just call ready macro to
not duplicate code within one inc file.
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> perhaps you missed this but I don't allow, I just call ready macro to
> not duplicate code within one inc file.
You're right, I did miss this.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Mon, 29 Oct 2001 18:19:33 +0100, "Rune" <run### [at] mobilixnetdk> wrote:
> > this macro is not on the list but I think it could be usefull
>
> Hmm, I don't know, so I'd like to hear the opinions of others. Is this macro
> useful enough for inclusion?
I still wait for the answer becouse I don't get strategy for rest of macros.
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"W³odzimierz ABX Skiba" wrote:
> I still wait for the answer becouse I don't
> get strategy for rest of macros.
I haven't got many opinions from others but ok, I'll include it.
Can anybody make it more effecient? ~130 lines is quite a lot for such a
macro.
Rune
--
3D images and anims, include files, tutorials and more:
Rune's World: http://rsj.mobilixnet.dk (updated Nov 5)
POV-Ray Users: http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sat, 10 Nov 2001 17:04:55 +0100, "Rune" <run### [at] mobilixnetdk> wrote:
> Can anybody make it more effecient? ~130 lines is quite a lot for such a
> macro.
It could be much shorten but as I showed in another thread some constructions
not work (http://news.povray.org/0qjittsg3bmv8422pj5egqvo8p4sg9p36h@4ax.com)
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
|
|
| |
| |
|
|
|
|
| |
|
|
