Mesh container class(or mesh tree structure)
- Currently we have two virtual coupling objects for laryngoscope(attached to the same Omni), one for handle, one for blade, because the meshes and textures are given separately.
- Use haptic device to move/rotate the mesh container, all child meshes will move along with the container.
- In other situations, we may want a local translation/rotate of the sub-meshes applied on top of the movement of the mesh container(for example, scissors).
- One solution is to construct custom classes for commonly used mesh collections (for ex. Two jawed tools)