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 830
    • Issues 830
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 234
    • Merge requests 234
  • 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
  • #17835
Closed
Open
Issue created Apr 07, 2020 by Ben Boeckel@ben.boeckel⛰Owner0 of 1 checklist item completed0/1 checklist item

Follow-up from "Add rendering ui"

The following discussion from !6470 (merged) should be addressed:

  • @michael.migliore started a discussion: (+1 comment)

    @ken-martin when configured the first time on linux, VTK_USE_X is not set yet and the factory do not create vtkXRenderWindowInteractor but vtkGenericRenderWindowInteractor.
    Two workarounds are possible:

    • Configuring VTK a second time fix the issue because VTK_USE_X is now set.
    • Use -DVTK_USE_X=ON explicitly when configuring VTK.

    The issue is similar on OSX with VTK_USE_COCOA.
    Imo, this should be fixed before 9.0 release.
    Quick fix: adding VTK::opengl in RenderingUI module dependencies where VTK_USE_X is defined but I'm not sure this is what we want.

    cc @mwestphal

Assignee
Assign to
Time tracking