We noticed that outline for a selected region behaves in a very strange way.
For oblique planes the outline does not fit to the selected pixels, but the shifting can't be predicted at all. So far we can not find any logical reason for that.

a) We checked the spacing of the image and the spacing stored in the

localStorage of the mapper and they are the same.

b) We checked outlining between different slices. That is where we found a new

very strange bug. For some cases the outline remains, even if there is no pixel
selected in current slice. And some times it depends on the direction how
you are going through slices (?????).

c) For slices at the 'begining of the image stack the error seems to be quite

small, when going through the stack the error varies.

d) Sometimes the outline is even outside of the image regardless wether we are at

the begining or at the end according to the image edges.

e) The shifting only occurs in directions where the spacing was recalculated.

Crosshair in center of Outline

We found something that might cause the bug.

In the attachments there are two screenshots showing that the crosshair is not in the center of the pixels of the image, but in the center of the outline. This means that either the image is shifted somehow or the outline and crosshair are wrong.

Crosshair not in center of pixel

MITK-1-0 keyword is obsolete, we use Target Milestones in the future.

This bug was discovered during testing of 2012-06, updating version. Target milestone is unspecified until general bug review, but feel free to fix it before.

This bug was discovered during testing of 2012-06, updating version. Target milestone is unspecified until general bug review, but feel free to fix it before.

This bug could not be fixed within the 2013-06 release and has medium severity. Setting target milestone to unspecified.

This bug could not be fixed within the release 2013-06. Setting its target milestone to unspecified