Skip to content
GitLab
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 832
    • Issues 832
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 238
    • Merge requests 238
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and 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
  • VTKVTK
  • VTKVTK
  • Issues
  • #368
Closed
Open
Issue created Nov 11, 2003 by Kitware Robot@kwrobotOwner

vtkLookupTable::DeepCopy() does not copy InsertTime and BuildTime

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


In vtkLookupTable::DeepCopy(), InsertTime and BuildTime are not copied. Thus, if the original LUT was built by manually inserting colors into the table, the copy will forget that fact (as InsertTime will be equal to BuildTime), and a subsequent Build() will call ForceBuild(), that will rebuild the table from the HSV ranges, erasing the manually inserted values.

I'm attaching a trivial patch that copies InsertTime and BuildTime too.

The patch is for the latest revision (1.90) on the release-4-2 branch.

Assignee
Assign to
Time tracking