Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • S Slicer
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 40
    • Merge requests 40
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Sam Horvath
  • Slicer
  • Merge requests
  • !432

ENH: VolumeRenderingModuleWidget: Extend API adding two new signals:

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Davide Punzo requested to merge github/fork/jcfr/add-VR-module-widget-signal into master Dec 10, 2015
  • Overview 3
  • Commits 1
  • Pipelines 0
  • Changes 2
  • newCurrentDisplayNode
  • newCurrentMRMLVolumeNode

**** WIP ****

Why ?

signals to synch the current MRMLVolumeRendeingDisplayNode from the VolumeRenderingModuleWidget to another ModuleWidgets.

if the signal approach is wrong, what about one of these two approaches (using MRML):

  1. storing the current VolumeRenderingDisplayNodeID in the vtkMRMLVolumeRenderingScenarioNode. or
  2. storing the current VolumeRenderingDisplayNodeID in the SelectionNode.

Davide.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: github/fork/jcfr/add-VR-module-widget-signal