|
![](/i/fill.gif) |
The issue is that blob components aren't independent objects.
You can fake it with macros and basically get the modularity you
seek, although no associated memory savings.
Dan
Andrew Cocker wrote:
>
> Hi Bob,
>
> Bob Hughes wrote in message <36A### [at] aol com>...
> >If you mean to still have those blobs influenced by a parent threshold
> >value yet within their own separate statement so there is a multiple
> >component blob but not multitudes blobs {?}), I saw someone mention that
> >before and they had a patched version to do so I believe. If not, I'm
> >not sure I understand the idea you have in mind.
>
> Yeah, that's what I mean. Check out my recent post to pov.binaries.animation to see
the
> kind of thing I'm attempting to do. I had to declare each component seperately,
rather
> than declare a small group of components once, and then re-use that group an
> additional number of times. The only other way I could do it was to declare a blob
object,
> and then use it within a union statement, but then of course, each blob object would
not
> react with its neighbour.
>
> Andy Cocker
>
> and### [at] acocker freeserve co uk
--
http://www.flash.net/~djconnel/
Post a reply to this message
|
![](/i/fill.gif) |