I know the difference between a union and an object, but for some reason,
the code is giving me an object error when logically the code makes sense. I
was able to get around the error by placing a union block around the object
and the nested #while loops. This is what the code looks like after I put in
the union block:

union {
object{Orbited}

#while (CountR <= Row_Orbs)
   #while (CountN <= Num_Orbs)
      object { Orbital translate <OrbitR, CountR, 0> rotate <0, CountN, 0> }
      #declare CountN = CountN+1;
   #end
   #declare CountR = CountR+1;
#end
}

For some reason I do not understand, that simple fix removes the error
without me changing the pairing of brackets nor any of the code despite the
union block.



----- Original Message -----
From: "Hughes, B." <omn### [at] charternet>
Newsgroups: povray.newusers
Sent: Monday, June 16, 2003 2:28 AM
Subject: Re: Problem with 'object' errors?


> "Jessie K. Blair" <jbl### [at] earthlinknet> wrote in message
> news:3eed5f60@news.povray.org...
> > Oddly enough, the problem vanishes if I simply put a union around the
> entire
> > thing. I would still like to know why that error would have occurred in
> the
> > first place.
>
> 'object' isn't like a union at all, it's more of a container for a single
> "object" so more can be done with it (scale, rotate, translate, add
texture,
> etc.), although it seems you might have thought so or at least figured it
> could "union" everything. If you remove it from the macro call, at the
very
> end of your script, it's okay; or union around just that part is okay, but
> not needed (unless you intend to do more things with it as a whole,
> afterward).
>
> Bob H.
>
>

Post a reply to this message