Resizing of the 2D windows does not trigger a rendering. This could be caused by a changed order of vtk and non-vtk rendering. Matthias, could you have a look at it?

a changed order of vtk and non-vtk rendering

?

(In reply to comment #2)

a changed order of vtk and non-vtk rendering

?

Markus F said your changes to the render windows changed the order of vtk and non-vtk rendering.

I can confirm this bug for linux: no updates in the 2d windows when resizing them.

Resizing of the 2D windows does not trigger a rendering.

cannot reproduce with a 32-bit windows debug, vs9.

strange, we recognized this bug with a win32 build, debug, vs9!

and:
VTK-5.4.2-QT-4.6.2_VC9.0_Bin
ITK-3.16.0_VC9.0_Bin
QT-4.6.2_VC9.0_Bin

can confirm the problem with the 3D window.

I'm currently looking for the exact revision that introduced the bug. Revision 24841 was still ok, that is after the rendering classes redesign. Maybe it's related to the RenderingManager changes. I will continue on Monday looking for the exact revision (git bisect is very helpful ...).

Ok, revision is between 25312 and 25328, have to leave now ...

Sorry, between 25296 and 25328, so most probably RenderingManager related ...

Bug is a 'side-effect' of T4991.

Somehow, the overall QT interaction for the renderWindow widget seems disabled. Thus, QmitkRenderWindow does not even invoke a mousepressed event. In consequence, rendering pipeline is not initiated.

added spec.

[SVN revision 25937]
FIX (#5276): Removing QmitkAbortEventFilter from Core and QmitkRenderingManager.

• QmitkRenderingManager now has the only task to include pending rendering requests into the qt pipeline

• wrt Mathias S., QmitkAbortEventFilter is currently not able to do its intended job: abort a volume rendering process.

[SVN revision 25938]
COMP (#5276): Removed include of qmitkaborteventfilter

Klaus, can you try if it works for you now?

looking good