1. Use of multiple RendingManagers no longer possible
1.1. Actual behavior
When creating a new QmitkRenderWindow with a distinct RenderingManager as parameter the corresponding BaseRenderer is still initialized using the global instance of mitk::RenderingManager.
Thus it is no longer possible to have several RenderWindows with distinct RenderingManagers
1.2. Expected behavior
The BaseRenderer corresponding to a new QmitkRenderWindow should be registered at the given RenderingManager. If no RM is given, the default RM shall be used.
2. Cause of the bug
Matthias forgot to implement this feature when adding the abstract baseclass mitkRenderWindowBase in his ambitions to facilitate QT-independent rendering
3. Proposed solution
Add RenderingManager as optional parameter for mitk::RenderWindowBase::Initialize(). This RM can be used to register the corresponding BaseRenderer. If no RM is given, the global instance will be used.
4. Affected classes
- mitkRenderWindowBase
5. How will the bugfix get tested?
will be tested automatically, as we cannot use multiple RenderingManagers right now