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 833
    • Issues 833
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 240
    • Merge requests 240
  • 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
  • #17973
Closed
Open
Issue created Aug 04, 2020 by Kit Chambers@batearedcollie

Wrapping VTK derived classes with non-standard names

Following discussion on

https://discourse.vtk.org/t/module-wrapping-classes-with-non-vtk-names/3905

It appears that the wrapping functions in VTK require class names to begin with VTK. It would be good to have the ability to wrap derived classes with non-standard names as well.

For example, if you have a data type like this

class myType: public vtkImageData
{
... blah blah ..
}

And an algorithm class like this

class myAlgorithm: public vtkImageDataAlgorithm
{
... blah blah ...

myType* = GetOutput(){
   return myType::SafeDownCast(this->GetOutputDataObject());
 }

... blah blah ...

}

Then the vtk python wrapping will skip/ignore the GetOutput method in myAlgorithm.

Assignee
Assign to
Time tracking