works! we can close this bug.

While closing the application QmitkSegmentationView::StdMultiWidgetClosed is called and a new StdMultiWidget is generated:
m_MultiWidget = this->GetActiveStdMultiWidget();

itk 3.16 histogramms can only count up to 2^24 samples
this results in this error

[SVN revision 20031]
CHG (#2900): update crosshair state in MenuWidget when SetWidgetPlanesVisibility is called in QmitkStdMultiWidget

I can check this..

The bi-modal shape model segmentation requires a multi-channel image e.g. a vector image of size 2 and type short (for two images):
itk::Image<itk::Vector<short,2>,3>

[SVN revision 29140]
CHG (#2893): Added additional vector size of 2 and 'short' as a possible type (N_VEC)

Hi Daniel,

ok... Now the application did not crashed anymore.

Hmmm.. I turned off 3D volume rendering in Preferences->Segmentation, but the Application is still crashing.

The application is still crashing when a new Segmentation will created for image Aufnahme.pic.gz.

ok.. works for me too.. We can close this bug..

[SVN revision 19779]
CHG (#2801): only DoubleClick will change the dataNode name.

Changes of RenderMenu behavior

[SVN revision 19610]
CHG (#2714): Implementation of all buttons without any functions are removed. Now, the menu Widget contains only three working functions: CrossHairMode, FullScreen and Property list for changing the layout design.

The zip-file includes two patches of the changes to revision 19609 and 19610. Furthermore it includes the original cpp and header of the QmitkRenderWindowMenu WITH the not-working buttons. For the case, the function "split widget horizontal, split widget vertical and close widget" will be implemented in next time, the old icons and implementation can be used from this files.

[SVN revision 19609]
CHG (#2714): define region of visibility of the menu widget. In 2D Render Windows the region is defined in the upper region of each window. In 3D in the upper right corner. The show/hide Event moved from enter-/leaveEvent to MouseEvent.

[SVN revision 19682]
CHG (#2714): instantiate m_Layout with 0, for showing the menuWidget when no Layout was set before.

[SVN revision 20118]
CHG (#2693): include ToolBar for expert (icon) view and set absolute min and max of sash container.

[SVN revision 19897]
CHG (#2693): To avoid empty space between the buttons and icons, the widget is automatic resized to the space of the visible buttons when size of the widget changed. Behavior is more outlook like.

[SVN revision 20265]
CHG (#2693): include styleSheet for active button

Application crashed during start up, when Perspective Switcher View is enabled. Output of QString::fromStdString(GetSite()->GetPage()->GetPerspective()->GetId()) is invalid.

[SVN revision 19667]
FIX (#2693): include while-loop for testing if currentId is in a Button Map. Include member for button height.

[SVN revision 19719]
CHG (#2693): include cherry::ISizeProvider to provide a minimum height of the widget.

[SVN revision 19712]
FIX (#2693): To avoid double-checked buttons in perspective view, the signal connection is changed to clicked() and setDown() is replaced by setChecked().

[SVN revision 19642]
ADD (#2693): add View for changing between different perspectives.

Create QmitkPerspectiveSwitcherView in Sandbox for changing between different perspectives. Depending on the size of the view widget, the pushButtons of the persperctives change between full-described buttons (icon + text) positioned among each other in the upper region AND small buttons (icon) positioned side by side in the lower region (like the left Toolbar in Microsoft Outlook).

We close this bug.

[SVN revision 22206]
FIX (#2660): cleaned up; removed tests for the ITKPixelType which is not set if you instantiate a mitk::PixelType;

[SVN revision 19761]
CHG (#2652): now the bundle generator create and set a standard icon (red quad) for the new View

[SVN revision 19250]
ENH (#2516): added several tests for the mitkToolManager. Added a security request in mitkToolManager::ActivateTool(int id)

is this really release 1.0 relevant?

set minimum width of the MenuWidget at 122 to position the widget correctly into the upper right corner.

Change Request

Change Request

ChangeRequest

Set minimum sizes of all objects in QmitkLevelWindowWidget.ui to ZERO for enlarging the Viewer space when WindowLevelWidget doesn't show up.

Change Request

closing bug

Markus F. suggested open cherry styled names. The names are also necessary for serialization.

The same behavior occures on the intial state of the application (without loading any images).

ChangeRequest

add render window names for each RenderWindow:
stdmulti.widget1
stdmulti.widget2
stdmulti.widget3
stdmulti.widget4

ChangeRequest

Does anybody need this? How many bundles are using this?

Replaced m_Image with itkImage in the method InternalCompute for calculating the volume of 4D images. This method is always called with a 3D or 2D image.

::Resize in vtkPropRender could be called from the qt resize event mechanism, and no openGL render context is given, so we removed following useless openGL statements.

This one is finished. we will close this bug.

when moving the bar into the center and then dragging the upper side to the topmost corner, everything is fine.

For catching the mouse event in the upper region of the levelWindowWidget the enterEvent was reimplemented. The position of the cursor is calculated by converting the global position to the local coordinates of the widget. With this position the mouseMoveEvent is called manually.

[SVN revision 25794]
FIX (#2188): reimplemented enterEvent to reactivate the str-drag on the upper side of the levelWindowWidget.

In the search for the bug, we discovered:

[SVN revision 21268]
ENH (#2185): added check for loading datastorage; fixed bug in pointset and surface node test

add render window names for each RenderWindow:
stdmulti.widget1
stdmulti.widget2
stdmulti.widget3
stdmulti.widget4

As suggested in T2389 we give the RenderWindow open cherry style unique names.

setParent by the initialization of the render windows. This works for the initial layout. but when you change the layout, it will still crash. We are working on a stable solution.

FRE Calculation Test

FRE Calculation Test

[SVN revision 21084]
CHG (#2118): remove Qt3 Support in GUI

Now, the menu widget is still displayed and moved to the correct position of the current renderWindow, when user activate the full-screen mode.
Also a new icon is included which replace the full-screen icon during the full-screen mode.

The Maximize Button is activated. If you click once, the actual window will maximize to fullscreen. If you click a second time, the former view design will be reconstruct. When you change in the Full-Screen Mode the LayoutDesign by the Property button, the FullScreen Mode is switch to off.

First working version of a flexible layout design is done. We close this bug.

Now all the exist layouts includes splitter, for changing the size and hide windows by moving the splitter to the border. Also you can change the layout design (MITK standard layouts) by the property menu of the widgetMenu.

Add a MenuBar in the top right corner of each render window. The menu bar is visible when the mouse enter the widget and is invisible when leaving the widget.
!For the moment, the menu buttons don't have any actions!

First version of an flexible layout design. Different splitters allow resizing and hiding widgets in a simple way, by moving the space between the different widget. (Revision #17404)

Added missing Modified() in SetAutoTopMostImage().
Fix in revision #17443.

still fixed! ;-)

Interpolation preview is fixed for the Qt4 version.

Markus F. has already committed his changes and has completed the work on this bug. Sven, can you take the bug again and see what's missing? Thank you

what is the status of this bug?

linked zooming in all 2D Renderwindows

The patch has a rudimentary implementation for this feature. We need a switch to turn this feature on and off. The right place for this is the mitkRenderingManager. We also need groups of 2D render windows which share same bahaviors...

linked zooming in all 2D Renderwindows

The zoom factor can be adjusted in the preference page with the provided patch. Following issues are missing: Save the zoomFactor persistent with the blueberry service; Show the right zoomFactor when opening the preference page; change request is not finished yet;

Is this still a issue?

Zoom Factor Property

[SVN revision 24575]
FIX (#1432): solved LAST vtkDebugLeak and enabled LiverSegmentationTestDriver again.

[SVN revision 24299]
COMP (#1432): Due to the last fix (revision 24266) a vtkDebugLeak occurs in the LiverSegmentationTestDriver. I disabled the test again and I will look at it next bugSquashing Party.

vtkDebug leaks are solved in all tutorial steps, public tests and all applications (opening, loading an image (or not), closing).

[SVN revision 24196]
FIX (#1432): Enable LiverSegmentationTestDriver for testing.

[SVN revision 24195]
FIX (#1432): Removed vtkDebugLeaks in MitkAnisotropicRegistration- and LiverSegmentationTestDriver. Now all tests whether in intern or extern are running fine.

[SVN revision 24266]
FIX (#1432): Revert changes. m_PolyDataSeries is deleted in mitkSurface.

[SVN revision 22724]
COMP (#1432): remove changes in mitkManualSegmentationToSurfaceFilterTest

[SVN revision 23107]
FIX (#1432): removed vtkDebugLeak in mitkRenderingManagerTest by deleting vtkRenWin correctly and call RemoveRenderWindow at the end of the test. Furthermore delete vtk variables in RenderingManager::AddRenderWindow instead of in RemoveRenderWindow.

[SVN revision 22722]
FIX (#1432): Resolved vtk Debug leaks of the tests concerning open source MITK. Still three tests are failing (mitkFactoryRegistrationTest, mitkManualSegmentationToSurfaceFilterTest and mitkPointSetFileIOTest).

[SVN revision 22734]
FIX (#1432): change variable order in the destructor