Skip to content
GitLab
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 83
    • Issues 83
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 14
    • Merge requests 14
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Gitlab will be updated February 2nd, between 8am and 9am EST (UTC-5). Gitlab will be offline during that time.

  • iMSTKiMSTK
  • iMSTKiMSTK
  • Issues
  • #16
Closed
Open
Issue created Jun 23, 2015 by Sreekanth Arikatla@sreekanth-arikatlaContributor

clean up smVAO and smVBO

After looking at smVAO, it looks like it was just smVBO, copied and then modified, as there are several member variables that aren't used, and at neamed/typed the same as in smVBO, most notably:

GLuint vboDataId; GLuint vboIndexId; QHash<smInt, smInt> dataOffsetMap; QHash<smInt, smInt> indexOffsetMap; QHash<smInt, smInt> numberofVertices; QHash<smInt, smInt> numberofTriangles;

Assignee
Assign to
Time tracking