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 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

Gitlab will be updated February 2nd, between 8am and 9am EST (UTC-5). Gitlab will be offline during that time.

  • VTKVTK
  • VTKVTK
  • Issues
  • #7818
Closed
Open
Issue created Oct 14, 2008 by Kitware Robot@kwrobotOwner

better mapping of cocoa concepts to vtk concepts

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


Assuming VTK uses the same concept as X11 and Win32 in their api (which is very likely), I suggest mapping these concepts for Cocoa...

NSView -- VTK WindowId n/a -- VTK DisplayId NSWindow -- new VTK concept, or keep it in Cocoa/Carbon implementations. Its possible for the code to get an NSWindow from an NSView, so one shouldn't be required to provide that info to vtkCocoaRenderWindow.

Assignee
Assign to
Time tracking