[Dir3d-l] members "on the fly" and memory

[Iñigo de Gracia]

It seems that I slipped on that bit of the 3d member, we are only 
creating vectorShapes.

That said, I suppose that  you could use a clone of a member to easily 
keep track of "state".

i

Colin Holgate escribió:
> At 4:22 PM +0200 5/8/07, Lucas Meijer wrote:
>>> What's an example situation where you need more than one 3D member?
>> Sometimes it makes sense to do raycasting in a seperate scene (with 
>> simpler geometry),
>> instead of addToWorld()/removeFromWorld() ing it in one main scene 
>> all the time.
>
> What's an example case where you'd need several 3D members?
>
> _______________________________________________
> Dir3d-l mailing list
> Dir3d-l at nuttybar.drama.uga.edu
> http://nuttybar.drama.uga.edu/mailman/listinfo/dir3d-l
>