Bug may also happen when no tool is active:

Deleting the bin/CTK-* folders -> Superbuild -> Blueberry Clean lets the workbench start again.

--Blueberry-Clean and manually deleting the temporary files did not help.

(In reply to Nils Lichtenberg from comment #5)

The connection in ctkDICOMTableView in line#128

QObject::connect(this->tblDicomDatabaseView, SIGNAL(doubleClicked(const
QModelIndex&)), q, SIGNAL(doubleClicked(QModelIndex)));

is registered twice.

Changing the connection to

QObject::connect(this->tblDicomDatabaseView, SIGNAL(doubleClicked(const
QModelIndex&)), q, SIGNAL(doubleClicked(QModelIndex)), Qt::UniqueConnection);

solves the problem.

I'm not sure if this is a CTK bug or if the encapsulation of CTK in MITK
leads to the doubled registration.

The connection in ctkDICOMTableView in line#128

User is responsible to select the correct image.

(In reply to Andreas Fetzer from comment #1)

What do you actually mean with 3D display? The volume rendering?

Additionally, information should be added which of the selections is used as foreground for the "Difference" operation. (e.g. A-B or B-A)

Bug cannot be reproduced.

(In reply to Git Admin from comment #8)

User lichtenn has pushed new remote branch:

bug-18084-Geometry_not_initialized_properly_on_4DImages

Deactivation of MitralAnnulusOptimizer Test

Problem is probably related to TimeGeometry changes (bug-17209).

[56fe74]: COMP Merge branch 'bug-18084-MItralAnnulusOptimizerTestFails'

Merged commits:

2014-09-11 13:40:26 Nils Lichtenberg [3a0624]
Deactivated MitralAnnulusOptimizerTest

The bug may be related to the geometry redesign, but further investigation is necessary.

After writing an MITK test, we are sure that this is bug in MITK geometry.

Further investigation revealed that mitk::Image::GetSlicedGeometry returns NULL for timesteps that are != 0 or have not been viewed/rendered before.

[3d0d31]: Merge branch 'bug-18031-Workbench-crash-on-entering-transfer-func-valu

Merged commits:

2014-08-20 15:45:06 Nils Lichtenberg [b29680]
Now adding the same histogram to the color widget like to the other widgets. The histogram is used to check for the valid range of input.

[f9018a]: Merge branch 'bug-18027-VolumeVis-transfer-func-not-updated'

Merged commits:

2014-08-20 15:17:06 Nils Lichtenberg [981d9a]
Transfer function points now get updated on each edit within the corresponding QLineEdit.

Tried to reproduce this on Linux with current master.

(In reply to Nils Lichtenberg from comment #2)

Tried to reproduce this on Linux with current master.

Initial console output is the same as in attachment.

Additionally, the transfer is marked as successful:

GET responses report for study:
1.2.276.0.7230010.3.1.2.69332360.5336.1415132775.623
1 images transferred, and
0 images transferred with warning, and
0 images transfers failed
Retrieve success

... but no image is transferred to local storage.

The DCMTK module has two executable storescp files, in DCMTK-install and
-build.
When running the DICOM plugin, the path points to the install folder. This
executable is not runnable from console, but the one in the build folder is.
Is there any difference?

The opacity slider updates the opacity value in the properties window and the render windows live.
Am I looking at the wrong spot?

This bug was produced on a linux machine with following locale config:

Probably refers to http://bugs.mitk.org/show_bug.cgi?id=16328

First investigation:
-Internally the seed point value is temporarily stored as an integer
-> fails for 0..1

Requesting core modification for doxygen file:
Core/Documentation/Doxygen/Concepts/DataInteraction.dox

[faa0f7]: Merge branch 'bug-17837-StatemachineDocumentation'

Merged commits:

2014-06-04 17:20:43 Nils Lichtenberg [164dd9]
Merge branch 'bug-17837-StatemachineDocumentation' of mitk.org:MITK into bug-17837-StatemachineDocumentation

[e26039]: Merge branch 'bug-17830-trac-3517-display-geometry-zoom-with-1-0-facto

Merged commits:

2014-06-11 14:31:34 Nils Lichtenberg [6e939e]
Merge remote-tracking branch 'pullReq-17830/bug-17830-trac-3517-display-geometry-zoom-with-1.0-factor' into bug-17830-trac-3517-display-geometry-zoom-with-1.0-factor

I could not reproduce the case that the origin changes while the scale factor remains constant.

mitk.org/ChangeRequests/17830

[046d29]: Merge branch 'bug-17809-On-Confirm-Segmentation-Crash'

Merged commits:

2014-05-28 13:49:56 Nils Lichtenberg [02b25e]
clearing segmentation on confirming segmentation if the shape is not closed

[117c15]: Merge branch 'bug-17801-crash-at-fill-contour'

Merged commits:

2014-05-14 16:42:07 Nils Lichtenberg [42b729]
Issue has been fixed by returning empty VtkPolyData object for the less than 3 points case.

[2ef13f]: Merge branch 'bug-17802-crash-on-contour-point-selected'

Merged commits:

2014-05-14 16:47:26 Nils Lichtenberg [26cc45]
Clear contour if point deletion results in one single point left

[b4d26f]: Merge branch 'bug-17772-stepper-getter-methods-should-be-const'

Merged commits:

2014-05-02 23:08:52 Taylor Braun-Jones [af64b8]
COMP: Cons-correctness fixes for Stepper getters

What Sebastian described still happened to me during the release check.
As a quick fix the user could be notified that the operation only works on 3D segmentations

[2d1c08]: Merge branch 'bug-17357-disable-tool-interaction-in-3d'

Merged commits:

2014-05-28 15:31:12 Nils Lichtenberg [5bbc3d]
Added call of CanHandleEvent to each Action

This seems to be a windows specific bug.

What's the status of this bug?

What's the status of this bug?

is T18244 a duplicate of/related to this bug?

Volume visualization checklist test 11 refers to the Grayvalue -> Color Widget.
For the Grayvalue -> Color widget the behaviour is correct.

The points can be set out of the visual range of the graph and thus out of the gray value range of the image. Is it that what you mean?

[9967b3]: Merge branch 'bug-16038-Transferfunction-anchor-points-out-of-valid-ra

Merged commits:

2014-07-23 14:42:51 Nils Lichtenberg [512272]
resolved by restricting transfer function points to hisogram range

[87d79e]: Merge branch 'bug-14849-Volume-visualisation-lineEdit-too-small'

Merged commits:

2014-08-13 15:10:25 Nils Lichtenberg [67f190]
Merge branch 'bug-14849-Volume-visualisation-lineEdit-too-small' of mitk.org:MITK into bug-14849-Volume-visualisation-lineEdit-too-small

Branch has been merged, can the bug be set to resolved?

Closing this bug since the request is already implemented.

This feature is already implemented (for rightMouse + ctrl + moveMouse) but not active in the default interaction config. See bug branch

[8e2a46]: Merge branch 'bug-13969-Transferfunction-Point-Loses-Focus'

Merged commits:

2014-07-23 13:53:28 Nils Lichtenberg [311699]
QmitkTransferFunctionCanvas::AddFunctionPoint now returns an integer with the index of the newly set point. The return value is set as the index to focus.

What's the status of this bug?

What's the status of this bug? Is it ready to merge?

What's the status of this bug?

The bug-8957-ProofReadingDocumentation2 branch contains the changes proposed by the two interns (early august) and is ready to be merged.