I know there is workaround with functions, macros, pigments and other things but
I vote for:

  #declare Image=image_map{...}

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 know there is workaround with functions, macros, pigments and other things but
> I vote for:
> 
>   #declare Image=image_map{...}

#declare Image = pigment { image_map {...} }

object { my_object pigment { Image } }

-- 
Ken Tyler

Post a reply to this message

> > I know there is workaround with functions, macros, pigments and other things but
> > I vote for:
> > 
> >   #declare Image=image_map{...}
>
> #declare Image = pigment { image_map {...} }
> object { my_object pigment { Image } }

As I said I know about such workarounds. That's why I didn't wrote 'help needed'
however thanks for good intentions. :)

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 know there is workaround with functions, macros, pigments and other things but
> > > I vote for:
> > >
> > >   #declare Image=image_map{...}
> >
> > #declare Image = pigment { image_map {...} }
> > object { my_object pigment { Image } }
> 
> As I said I know about such workarounds. That's why I didn't wrote 'help needed'
> however thanks for good intentions. :)

I am not so sure that this qualifies as a "workaround". It is simply
what the parser expects since the image_map is one possible component
of a pigment.

-- 
Ken Tyler

Post a reply to this message

"Ken" wrote:
> I am not so sure that this qualifies as a "workaround".
> It is simply what the parser expects since the image_map
> is one possible component of a pigment.

I'd like to be able to declare separately anything that appears inside {...}
brackets. I think ABX was thinking in the same lines, or perhaps partly so.

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 Tue, 20 Nov 2001 07:14:29 -0800, Ken <tyl### [at] pacbellnet> wrote:
> I am not so sure that this qualifies as a "workaround". It is simply
> what the parser expects since the image_map is one possible component
> of a pigment.

I know 'color_map' 'image_map' 'pigment_map' are only names but according to
'_map' appendix IIRC only image_ and bump_ can't be declared. When you use the
same image as bump_map then it allocates space for image twice. So ideal
situation could be something like:.

#local Image=image{png "imagefile.png"}
#local P=pigment{image_map{image{P} image_modifiers}}
#local N=normal{bump_map{image{I} bump_modifiers}}

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

:   #declare Image=image_map{...}

  Perhaps the closest thing currently (besides making it just a pigment)
would be making it a pigment function. The advantage of this is over declaring
a pigment is that you can use the function anywhere:

#declare Image = function { pigment { image_map { ... } } }
...
  pigment { function { Image(x,y,z) } }
  normal { function { Image(x,y,z) } }
  interior { media { density { function { Image(x,y,z) } } } }
...

-- 
#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 know there is workaround with functions, macros, pigments and other things but
> I vote for:
> 
>   #declare Image=image_map{...}
> 

If there is something like that i would vote for a different solution that
includes heightfields for example, of course i could use a
function-image_map construction, but having a possibility to declare
images for both heightfields and image maps and at the same time avoiding
double storage of data would be a good idea IMO.

Christoph

-- 
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other 
things on: http://www.schunter.etc.tu-bs.de/~chris/

Post a reply to this message

On Tue, 20 Nov 2001 17:13:58 +0100, Christoph Hormann <chr### [at] gmxde>
wrote:
> having a possibility to declare
> images for both heightfields and image maps and at the same time avoiding
> double storage of data would be a good idea IMO.

That's what inspired me - storage of images.

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

: That's what inspired me - storage of images.

  And why function { pigment { image_map { ... } } } doesn't do this?

-- 
#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