Page MenuHomePhabricator
Create Task
Maniphest T4991

RenderingManager: Possiblity to use multiple managers
Closed, ResolvedPublic
Actions

Description

  • Some MITK classes easily use the mitk::RenMan::GetInstance() singleton.
  • This limits the RenMan usage to the global instance and is prone to errors

If an application uses some render windows with varying data in differing parts of the application, we want to have the possibility to manage the rendering process independent for each window.

Thus, the rendering manager should always be instantiated by means of:
mitk::BaseRenderer::GetInstance(vtkRenderWindow*)->GetRenderingManager()

core modification requested, some spec will be provided.

Related Objects

Event Timeline

baumhaue added projects: MITK, Bugzilla.Aug 6 2010, 6:55 PM
maleike added a subscriber: maleike.Aug 7 2010, 4:13 PM

Please first write at least a rough sketch on the wiki page, then request the flag. I'm resetting the flag, so I'll get mailed when it is requested again.

baumhaue added a subscriber: baumhaue.Aug 9 2010, 10:58 AM

added spec.

baumhaue added a comment.Aug 9 2010, 11:20 AM

[SVN revision 25305]
FIX (#4991): Possiblity to use multiple managers

Some MITK classes easily use the mitk::RenMan::GetInstance() singleton.
This limits the RenMan usage to the global instance and is prone to errors.

If an application uses some render windows with varying data in differing parts
of the application, we want to have the possibility to manage the rendering
process independent for each window.

Thus, the rendering manager should always be instantiated by means of:
mitk::BaseRenderer::GetInstance(vtkRenderWindow*)->GetRenderingManager()

baumhaue mentioned this in T5276: No Mouse-Events in Renderwindow.Sep 3 2010, 3:27 PM
MITK · MIC · IMSY · DKFZ