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 740
    • Issues 740
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 198
    • Merge requests 198
  • 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
  • #9642
Closed
Open
Created Oct 01, 2009 by Kitware Robot@kwrobotOwner

coincident topology resolution methods in vtkMapper should not be static

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


I am wondering why the coincident topology resolution methods in vtkMapper are implemented as static methods. With the new vtkPainter based rendering it would be possible to render surfaces with different polygon offsets to enable overlapping surfaces. Therefore, each vtkMapper must have its own coincident topology resolution settings.

Assignee
Assign to
Time tracking