Looking at the `mitk::RenderingManager` there are several functions that are basically doing the same. They only differ in their given parameters and therefore need to process the given data slightly differently.
However, there is sometimes a different logic although they should do the same and I wonder why that is, e.g.:
https://phabricator.mitk.org/source/mitk/browse/develop/Modules/Core/src/Controllers/mitkRenderingManager.cpp$447 uses `initializeGlobalTimeSNC` whereas https://phabricator.mitk.org/source/mitk/browse/develop/Modules/Core/src/Controllers/mitkRenderingManager.cpp$374 does not use this variable.
On the other hand,
https://phabricator.mitk.org/source/mitk/browse/develop/Modules/Core/src/Controllers/mitkRenderingManager.cpp$331 extends the bounding box to have "an extent bigger than zero in any direction" whereas
the function in https://phabricator.mitk.org/source/mitk/browse/develop/Modules/Core/src/Controllers/mitkRenderingManager.cpp$426 does no such thing.
Also, only in https://phabricator.mitk.org/source/mitk/browse/develop/Modules/Core/src/Controllers/mitkRenderingManager.cpp$385 `mitk::RenderingManagerViewsInitializedEvent()` is called, although a a rendering request / view initialization happened in other functions as well.
There is also an old comment in https://phabricator.mitk.org/source/mitk/browse/develop/Modules/Core/src/Controllers/mitkRenderingManager.cpp$297 that says "Remove old function, so only this one is working." so maybe that's a hint to remove the later function?
I found this while working on D517 to separate the rendering from the view initialization.
If we can clarify this we might be able to remove many lines of code and simplify the code that is concerned with view initialization, which would bring us a step forward in finding a good solution for related tasks, such as T28490, T27613 and T26496