![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
> Now I found your post that it is rather limitation. If this
> is confirmed limitation by the Team then it is sad fact for me.
It's not confirmed by the Team. I don't really know if it's just a
limitation but I'm fairly sure it is.
> I found way to make simple OOP for SDL with this.
What prevents you from using the method with the counter?
> There is another thing connected with Parse_String
> http://news.povray.org/tlstqtsgocagvejfs6knd6buql6tqo2qn3@4ax.com
I'll look into this.
Rune
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Fri, 2 Nov 2001 15:01:23 +0100, "Rune" <run### [at] mobilixnet dk> wrote:
> "W?odzimierz ABX Skiba" wrote:
> > Now I found your post that it is rather limitation. If this
> > is confirmed limitation by the Team then it is sad fact for me.
>
> It's not confirmed by the Team. I don't really know if it's just a
> limitation but I'm fairly sure it is.
IIRC you can be right. There was fast macro patch within megapov based on
remebering content of macro in memory insted of file. Unfortnatelly it is part
of "Not part of 3.5" from status report.
I just found clear sentence within documentation "Calling a macro in another
file therefore requires that the other file be opened and closed for each call.
Normally, this overhead is inconsequential; however, if you are calling the
macro many thousands of times, it can cause significant delays. A future version
of the POV-Ray language will remove this problem."
I hope "future" mean 3.5a ;-)
> > I found way to make simple OOP for SDL with this.
>
> What prevents you from using the method with the counter?
nothing special. just hundreds of files :-(
I'm trying to prepare article about it for p.a-u
> > There is another thing connected with Parse_String
> > http://news.povray.org/tlstqtsgocagvejfs6knd6buql6tqo2qn3@4ax.com
>
> I'll look into this.
Thanks
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
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Skiba <abx### [at] babilon org> wrote:
> I just found clear sentence within documentation "Calling a macro in another
> file therefore requires that the other file be opened and closed for each
call.
> Normally, this overhead is inconsequential; however, if you are calling the
> macro many thousands of times, it can cause significant delays. A future
version
> of the POV-Ray language will remove this problem."
>
> I hope "future" mean 3.5a ;-)
4.0 if you are lucky.
Thorsten
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Fri, 02 Nov 2001 18:02:07 +0100, "Thorsten Froehlich" <tho### [at] trf de>
wrote:
> > I hope "future" mean 3.5a ;-)
>
> 4.0 if you are lucky.
then timidly I wait for next megapov
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
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Skiba <abx### [at] babilon org> wrote:
>> > I hope "future" mean 3.5a ;-)
>>
>> 4.0 if you are lucky.
>
> then timidly I wait for next megapov
Keep in mind that behind most not included features there are serious
technical or design problems. I am not saying anything about this
particular feature, but in general, you should not expect to find all "lost"
features in a future MegaPOV that is based on 3.5 - it might well be that
POV-Ray 3.5 breaks more than a few patches that are currently part of
MegaPOV 0.7...
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trf de
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Fri, 02 Nov 2001 18:52:43 +0100, "Thorsten Froehlich" <tho### [at] trf de>
wrote:
> Keep in mind that behind most not included features there are serious
> technical or design problems.
I thought about it this way. I found explanation for my problem and now I can
work with workarounds. Don't spent your time with such details. Go! Go to other
bugs :-) POV 3.5 is my favourite tool.
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
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Warp <war### [at] tag povray org> wrote:
: * When outputting to PNG, the wrong gamma correction value is written to it.
: The value 1.0 is always written as gamma to the PNG, which is wrong.
AFAIK this has been fixed (for next beta).
: * Focal blur aperture has no effect with camera types other than the
: persective one
And this is being taken care of (but not necessarily fixed for the next
beta).
--
#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
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Wasn't it W3odzimierz ABX Skiba who wrote:
>On Thu, 1 Nov 2001 07:29:29 +0000, Mike Williams <mik### [at] nospam please>
>wrote:
>
>> Since nobody else wanted to take this on, and since I've got a bit of
>> leisure time, I'll have a bit of a go. There may well be things that
>> have fallen through the gap between when Rune stopped and I started
>> collecting the info.
>
>you missed this
>
>Bug with declaration with no dimensions
>http://news.povray.org/scpitt851apfq5r6qtsoi1vpupt77g829s@4ax.com
>I don't know it is confirmed or not (Ron answered but no change within
>beta 7)
Is this a bug or a documentation error? Is there a case where we might
want to write "#local A=array;" and have it behave like this?
I'm not collecting documentation errors.
--
Mike Williams
Gentleman of Leisure
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Wasn't it Mike Williams who wrote:
>The "unconfirmed" section at the end is there for my convenience. It's
>easier for me to capture the information when I first see it rather than
>waiting for a confirmation to be posted.
I guess this turned out to be a bad move. I'll continue to capture
unconfirmed bug information, but I don't think I'll post it again.
Several people asked for unconfirmed bugs to be added to the list. I've
added the details to my database, but they won't appear in the known
bugs posts until they are confirmed.
--
Mike Williams
Gentleman of Leisure
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
> On Thu, 1 Nov 2001 07:29:29 +0000, Mike Williams <mik### [at] nospam please>
> wrote:
>
>> Since nobody else wanted to take this on, and since I've got a bit of
>> leisure time, I'll have a bit of a go. There may well be things that
>> have fallen through the gap between when Rune stopped and I started
>> collecting the info.
>
> you missed this
>
> Bug with declaration with no dimensions
> http://news.povray.org/scpitt851apfq5r6qtsoi1vpupt77g829s@4ax.com
> I don't know it is confirmed or not (Ron answered but no change within
> beta 7)
It's confirmed. I even know what causes it, but I haven't had time to fix it
yet. I did take the minute or so it took to enter it in the Team's bug
database, though.
--
plane{-z,-3normal{crackle scale.2#local a=5;#while(a)warp{repeat x flip x}rotate
z*60#local a=a-1;#end translate-9*x}pigment{rgb 1}}light_source{-9red 1rotate 60
*z}light_source{-9rgb y rotate-z*60}light_source{9-z*18rgb z}text{ttf"arial.ttf"
"RP".01,0translate-<.6,.4,.02>pigment{bozo}}light_source{-z*3rgb-.2}//Ron Parker
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |