We closed this forum 18 June 2010. It has served us well since 2005 as the ALPHA forum did before it from 2002 to 2005. New discussions are ongoing at the new URL http://forum.processing.org. You'll need to sign up and get a new user account. We're sorry about that inconvenience, but we think it's better in the long run. The content on this forum will remain online.
IndexProgramming Questions & HelpOpenGL and 3D Libraries › Shapes3D changes in post 1.7.0 versions
Page Index Toggle Pages: 1
Shapes3D changes in post 1.7.0 versions (Read 1139 times)
Shapes3D changes in post 1.7.0 versions
May 1st, 2010, 4:25am
 
In future versions of Shapes3D there is one change that will significantly alter its behaviour but will only affect existing sketches that have created composite shapes through the use of the method
Code:
addShape(aShape); 



The composite shape feature can be seen in the Earth/Moon example that comes with the library. Where there are 2 Ellipsoids earthand moon; a composite shape was created with
Code:
 earth.addShape(moon); 



In this example the earth object is the parent and the moon object the child.

In versions up to and including 1.7.0 when the parent is made invisible the children are unaffected so
Code:
earth.visible(false); 

would hide the earth but leave the moon visible.

There were good reasons for doing this at the time, but later versions provided features that made this unnecessary, so in the next version if a parent is made invisible then the children will not be displayed which is a more logical behaviour.

If this affects your sketch and you are not sure how to overcome it then let me know.
Smiley
Page Index Toggle Pages: 1