Es handelt sich um einen bekannten Bug in der MESA:

New remote branch pushed: bug-14146-Mesa-Flickering

braucht laut Markus kein Core Modification flag.

Should be no problem, as it is only called if planar figures has been marked as "closed" object.

mesa flickering

First working, windows only prototype implementation pushed:
http://mitk.org/git/?p=MITK.git;a=commit;h=bbe61ec8222aa990d64d6ed7ab860c6fd1811d8b

completed implementation and documentation.

OutOfProcess dump does not permanently use a separate process, but only temporarily.

We can leave this open but remove the blockers, as it does not block them any more.

To load a dump file:

http://mbits/cdash/viewBuildError.php?buildid=48502

patch

patch

[SVN revision 27456]
ENH (#5958): Fixed ColorProperty bug where "selected" property is set, but no specific color is defined. Using default color, again.

[SVN revision 27366]
ENH (#5958): Enhance ImageGLMapper2D to allow for hover and selection effects
Analogous to the PlanarFigureMapper, the ImageMapper2D shall be enhanced to
support for hover and selection effect by means of the property-mechanism.

[SVN revision 27086]
ENH (#5874): mitk::FileReader/FileWriter to allow for writing/reading from memory buffers
See Wiki specification.

Yes, QVTK2-Widget is just some other QT Integration of the VTK Rendering. It should not affect our rendering mechanism itself, but allow for better GUI integration of the rendering widgets along with up-to-date QT and VTK.

Thomas, nutzt MITK bereits das QVTK2 Widget, das mit VTK 5.8 eingeführt wurde?

Current Open-Source MITK Patch

Example Result

Some more backgrounds about the Qt Scene Graph:
http://labs.qt.nokia.com/2010/05/18/a-qt-scenegraph/

Example Result

Current Open-Source MITK Patch

patch for ./mitk dir.

needs core modification, c.f. attached patch + spec. document

added a patch containing the proposed solution (about five lines). added spec.

[SVN revision 26232]
ENH (#5291): added possibility to log into an additional OutputWindow on base of itk::OutputWindow.

patch for ./mitk dir.

FAZIT of evaluation:

A successfully compiled ExtApp (Debug) and linked to release-CRTs fails to load plugins. Poco is looking for the release-named ones without 'd' suffix.

Yes, removing the hard-coded /D_DEBUG in Poco's Cmake code makes makes it possible to link against Release-CRTs.

[SVN revision 26139]
FIX (#5281): add the _DEBUG flag hardcoded for all compiles besides MSVC.

Mixing of runtimes may cause heap corruption:

[SVN revision 26117]
COMP (#5281): disable POCO Flag _DEBUG, add POCO_NO_AUTOMIC_LIBS instead. This will allow for successfully compiling Poco against release runtimes (also as debug targets)

POCO_NO_AUTOMIC_LIBS defined works well to build POCO, but all Libs using POCO require also this define to be set (if we want to avoid any changes to the POCO sources).

Option /MD is for linking against release runtime. If set this way, the preprocessor definition _DEBUG (/D_DEBUG) must not be set also.

[SVN revision 26110]
ENH (#5281): disable POCO Flag _DEBUG, add POCO_NO_AUTOMIC_LIBS instead. This will allow for successfully compiling Poco against release runtimes (also as debug targets)

[SVN revision 26116]
COMP (#5281): revert

added spec.

Bug is a 'side-effect' of T4991.

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

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

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

a changed order of vtk and non-vtk rendering

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

can confirm the problem with the 3D window.

[SVN revision 25746]
COMP (#5229):
remove poco includes

[SVN revision 25747]
COMP (#5229):
remove poco includes

[SVN revision 25744]
COMP (#5229):

COMP (#5160): use of 'nullptr' instead of 0;

[SVN revision 25664]
COMP (#5160): use of 'nullptr' instead of 0 only in vs2010

[SVN revision 25665]
FIX (#5160): use of 'nullptr' instead of 0 only if supported

[SVN revision 25662]
COMP (#5160): use of 'nullptr' instead of 0;

added spec.

[SVN revision 25305]
FIX (#4991): Possiblity to use multiple managers

[SVN revision 26803]
ENH (#4735): enhanced the qt free render window example to reflect some little simplified QmitkStdMultiWidget behaviour.

[SVN revision 26857]
ENH (#4735): added std::map to store mouse button state during mouse move interaction

[SVN revision 26774]
FIX (#4735): fixed interaction issues in non-qt mitk

Example is implemented and works, see ..\Applications\Tests\QtFreeRender

Current status of this bug:

[SVN revision 25339]
ENH (#4735):

[SVN revision 24834]
ENH (#4735): QT independent rendering with MITK_CORE_EXPORT

Rendering so far is no big problem.

[SVN revision 26473]
FIX (#4735): fixed naming issue of render window

[SVN revision 24830]
ENH (#4735): QT independent rendering with MITK_CORE_EXPORT

[SVN revision 25514]
CHG (#4735): clean up memory leaks

[SVN revision 24838]
ENH (#4735): QT independent rendering with MITK_CORE_EXPORT

tried to reproduce again after svn update, but failed.

navigate also means move, pan, zoom etc.
Otherwise the bug might not occur.

cool project. Also interesting for 3m3.

less time effort than planned

[SVN revision 22970]
ENH (#3628): added arrow tool, scale invariant rendering, serialization

Please, make some statement about what this test shall cover.

If I try with "file->open":

dicom import error

dicom import error

reassign to 3m3 guru.

Is this only a 3M3 specific bug?

[SVN revision 21281]
ENH (#3284): merged QT CPACK installation commands of 3M3 and the conventional installer