Hi Sandy, Christoph,
thanks for dealing with this.
A little addition. Meanwhile I noticed that there is a this function:
QmitkAbstractView::RequestRenderWindowUpdate(mitk::RenderingManager::RequestType
requestType)
that does similar for plugins. It uses the rendering manager of the active
render window part, instead of the global rendering manager instance.
Cheers,
Miklos
On 23 July 2014 13:27, Engelhardt, Sandy <
[email protected]> wrote:
> Hi Miklos,
>
>
>
> thank you for reporting your request.
>
>
>
> We need to discuss about this issue and let you know soon about our
> opinions on it.
>
> However, we created a bug regarding the issue (bug 17936).
>
> http://bugs.mitk.org/show_bug.cgi?id=17936
>
>
>
> Best,
>
> Sandy and Christoph
>
>
>
> *Von:* Miklos Espak [mailto:[email protected]]
> *Gesendet:* Freitag, 11. Juli 2014 12:28
> *An:* mitk-users
> *Betreff:* [mitk-users]
> mitk::RenderingManager::GetInstance()->RequestUpdateAll()
>
>
>
> Hi,
>
>
>
> we have an application in which we provide two editors, let's call them
> MITK Display (QmitkStdMultiWidgetEditor) and DnD Display (our custom one).
>
>
>
> Until not so long ago both of them used the global rendering manager
> instance. But when a new image is opened,
> InitializeViewsByBoundingObjects(dataStorage) is called for the global
> rendering manager, that calculates a new time geometry based on the
> globally visible images in the data storage. This messes up the geometry in
> the DnD Display.
>
>
>
> There is a preference to suppress the InitializeViewsByBoundingObjects
> call, but it's useful only if you use only the DnD display (with the global
> rendering manager), but not both.
>
>
>
> So, I changed the DnD Display to use its own rendering manager. But then
> many MITK plugins stopped working properly because they update the screen
> by calling RequestUpdateAll on the global rendering manager.
>
>
>
> Would it be possible to change these calls to use the 'current' rendering
> manager?
>
>
>
> Something like:
>
>
>
> mitk::GlobalInteraction::GetInstance()->GetFocusManager()->GetFocused()->GetRenderingManager()
>
>
>
> Or (better) provide a static
> mitk::RenderingManager::GetFocusedRenderingManager() function that returns
> the rendering manager of the focused renderer, and just replace the
> GetInstance calls to this?
>
>
>
> Does this makes sense?
>
>
>
> Cheers,
>
> Miklos
>
>
>
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
