Thanks for the answer Does it make sense that my Shape3D sub classes implements this interface and so responsibility of changing remains within the Shape class. Is their any resaon why this interface is not implemented in existing classes.

Thanks for the answer Does it make sense that my Shape3D sub classes implements this interface and so responsibility of changing remains within the Shape class. Is their any resaon why this interface is not implemented in existing classes.

Well it doesn't matter from where update() is called (as long as it is not when the canvas is rendering.By "existing classes" you mean all those in com.xith3d.* and org.xith3d.* ? Shape3D isn't necessarily dynamic so don't need to implement GeometryUpdater or whatever.

Well it doesn't matter from where update() is called (as long as it is not when the canvas is rendering.By "existing classes" you mean all those in com.xith3d.* and org.xith3d.* ? Shape3D isn't necessarily dynamic so don't need to implement GeometryUpdater or whatever.

Yaa you are right Shape3D isn't necessarily dynamic so don't need to implement GeometryUpdater...it does'nt make sense to have unnecessary funtionality in the classes.

java-gaming.org is not responsible for the content posted by its members, including references to external websites,
and other references that may or may not have a relation with our primarily
gaming and game production oriented community.
inquiries and complaints can be sent via email to the info‑account of the
company managing the website of java‑gaming.org