Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • VTK VTK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 741
    • Issues 741
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 196
    • Merge requests 196
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTK
  • VTKVTK
  • Issues
  • #9614
Closed
Open
Created Sep 28, 2009 by Kitware Robot@kwrobotOwner

vtkVolumeTextureMapper3D::UpdateVolumes(...) calls Modified() method too early

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.


The calls to: this->SavedTextureInput = input; this->SavedTextureMTime.Modified();

should be placed at the end of the method instead of the begining, because at line 1103: input->GetPointData()->GetScalars()->GetRange(scalarRange, components-1); will modify the input->GetMTime() return value, so if we enter again in UpdateVolumes() the computations will be done without need of it.

This is needed since revision 1.80 of vtkDataArray.cxx because the method vtkDataArray::ComputeRange modify the MTime, wich was not the case before.

Assignee
Assign to
Time tracking