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
  • #5111
Closed
Open
Created May 29, 2007 by Kitware Robot@kwrobotOwner

coordinate conversions inconsistent

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


There are myriad ways to convert point locations between DISPLAY, VIEWPORT, VIEW, and WORLD coordinates. For example: vtkRenderer provides SetWorldPoint(), WorldToDisplay(), and GetDisplayPoint() which can be strung together to transform world coordinates to display coordinates; on the other hand vtkCoordinate provides SetCoordinateSystemToWorld(), SetValue() and GetComputedDoubleDisplayValue() which should do the same transformation.

However, the two methods don't always agree.

There are more examples of conversion inconsistency between vtkRenderer and vtkCoordinate, as demonstrated by the attached test case.

Assignee
Assign to
Time tracking