| Status | Assigned | Task | ||
|---|---|---|---|---|
| Wontfix | kislinsk | T2289 Redesign of MITK Rendering Mechanisms | ||
| Invalid | None | T2291 Automatic rendering update when data storage content changes | ||
| Wontfix | kislinsk | T2295 Implement general concept for off-screen rendering | ||
| Invalid | None | T2293 Standardize and simplify slicing of 3D data | ||
| Wontfix | None | T2290 Restructure mitk::RenderingManager | ||
| Resolved | None | T2294 Support usage of (VTK) shaders in mitk::SurfaceMapper | ||
| Wontfix | kislinsk | T2297 Sharing of rendering resources across views within the same render context | ||
| Resolved | None | T2292 RenderWindow specific handling of rendering ressources in Mappers | ||
| Wontfix | None | T2296 Decouple rendering back-end from VTK |
Event Timeline
Comment Actions
Resetting all bugs without active assignee flag to "CONFIRMED". Change status to IN_PROGRESS if you are working on it.
Comment Actions
Method 1: simplify VtkPropRenderer as mitkAssembly which collects vtkProps from datanodes..
Method 2: Use translate mechanisms from datastorage to vtk scenegraph
Problems / requirements:
- interoperability between mappers
- Overlay concept integration
- Video background rendering
- Layer properties for all objects
- update mechanisms
- rendering management (by whom will be rendered?)
- allow unified 2d/3d mitk mappers
Comment Actions
This task was automatically closed because it wasn't updated at least since July 2016 (over 2 years). Please re-open this task if you think that it is still relevant. This most probably means that you will resolve it.