Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • iMSTK iMSTK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 63
    • Issues 63
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 10
    • Merge requests 10
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • iMSTK
  • iMSTKiMSTK
  • Issues
  • #75

Closed
Open
Created Sep 26, 2016 by Nicholas Milef@NickMilefDeveloper

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)
Assignee
Assign to
Time tracking