If you load an image wiht large pixel spacing, im my case 1km = 1 000 000 mm (radar images), the crosshair disappears in coronal, sagital etc., in 3D it remains
It seems that the crosshair depth is something like 1mm and so it is not painted at larger spacings...
Maybe the line with of the crosshair should refer to the display with of the multi widget instead of the image spacing...
Can you please provide such an image to allow us to reproduce this?
However, I think MITK is designed for medical images which usually do not have such a large pixel spacing. We will discuss this and see if there is a need to support such imagetypes.
Since no data was provided (yet) and MITK is meant for medical images (which are in order of mm or cm) I will close this bug.
@Gerald: There are some ongoing changes because we want to integrate the SOA framework which is using meter is standard unit. Maybe this issue will get fixed in that context.
DICOM also supports CT/MR images from animals (there is an tag for it) so if i want to develop a CT for a blue whale then we are in meters^^
no, sorry for that small joke. It is not an urgend issue but in my opinion it should be quite easy to implement the crosshair size in reference to the whole extent of the scene. Its true that MITK is focused on medical terms but the basic core functionality like the multiwidget should work for all kind of data. If i buy a kinect and use it for image processing purposes instead of gaming it is also a lame excuse that no support exist... So please let MITK not beeing so closed-minded like Micros*...
best regards