|
 |
SharkD wrote:
> I was wondering if maybe in the next version the restriction on having
> only one type of object in an array could be lifted?
Just in case you don't know... All "objects" (3D shapes) are treated equal.
You can't have an array with some floats and some spheres, but you can have
an array with some spheres, some boxes, and a plane.
Post a reply to this message
|
|
|
|
"SharkD" <nomail@nomail> wrote:
> I was wondering if maybe in the next version the restriction on having only one
> type of object in an array could be lifted?
>
> Thanks!
>
> -Mike
I think, instead of permitting that, the introduction of a data-structure-like
language construct would be better from a scene organizational standpoint. It
would be neat to have a sort of object (from a programing standpoint) that can
hold values, textures, primitives, functions, etc. in a self-contained block.
The next step would be having macros associated with that object, and being able
to tell that object's macro to do some task on the object's data, or maybe even
have a listener type object that could do some task when certain other
conditions are met...
Ok, maybe I am going to far here. I'm just saying that it would be neat to have
a particle system in which the particles 'know' when they've hit other scene
objects and decide to bounce, or spawn particles themselves...
-Reactor
Post a reply to this message
|
|
