Open t3kt opened 9 years ago
This is similar to the existing module "type" defaults except at a different level. The subtype specifies what a module does and contains. This would generally mean what it is cloned from. Not all modules are reused, so it would be good to support modules that do not have a subtype.
The terminology is getting confusing. Maybe what is currently "type" (effect/source/chain) should be called "category" and this new thing should be called "type". Refactoring is difficult in TouchDesigner though..
This could clean up some of the module cloning/export problems. It would also make it easier to add small modules that don't require much configuration (e.g. the viewer module described in #35).