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 738
    • Issues 738
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 202
    • Merge requests 202
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTK
  • VTKVTK
  • Issues
  • #10121

Closed
Open
Created Jan 11, 2010 by Kitware Robot@kwrobotOwner

Wrong use of SetEnabled (int) method in some vtkInteractorObserver class destructor

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


Actually, vtkInteractorObserver class destructor make a call to "this->SetEnabled (0);"

The problem is that in c++, the virtual dispatching mechanism has a different semantics during construction and destruction of an object. So in this case, when we proceed to the destruction of a vtkInteractorObserver object, the SetEnabled(int) called method is the vtkInteractorObserver class definition (which is empty) and not the respective daughter method definition.

In other word, "this->SetEnabled(0);" call in the vtkInteractorObserver object destructor is useless, and all specialized classes are never disable itself at destruction.

Assignee
Assign to
Time tracking