jerome Posted March 31, 2015 Share Posted March 31, 2015 Hello, I'm currently coding the tube update feature.I want it easy : the user only needs to pass a path, a radius and a tessellation to build his tube. So I want he just passes another path and another radius to update the existing tube.As the number of tube vertices depends directly upon the tessellation, it can't be changed once the mesh is created. So the tessellation (as well as other properties like pathArray array or path3D, in the purpose not to reallocate memory each update call) should be stored with the tube object. TypeScript doesn't allow to add a new property to an instance of a class. The tube is just a particular ribbon. This ribbon is a Mesh instance.Actually, the tube mesh is just a big math helper for some complex sub-types of ribbons (tubular). Should I add some properties to the Mesh class although they aren't pertinent for other kinds of mesh : pathArray, path3D, tessellation ?they could be then re-used in almost any tubular kind of mesh, I guess, and this would be very easy to do Or do you (BJS architects) prefer another solution ?I don't think having a Tube class really is worth it imho ... Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.