Change Details

Status: As discussed in T25042 mapper should not show images if the time point selected in the Navigationslider is out of the time bound of the image. Currently at least the normal 2d/3d image mappers do so. To reproduce the problem: - load both test data from MITK-Data/3D+t-ITKIO-TestData. - place LinearModel_4D_prop_time_geometry top most - globally initialize - Go to a timestep >= 10 - LinearModel_4D_prop_time_geometry should no dissapear and only LinearModel_4D_arbitrary_time_geometry should be visible because it has the larger time bounds. This is not the case. The last time step of LinearModel_4D_prop_time_geometry is still possible.

Status: As discussed in T25042 mapper should not show images if the time point selected in the Navigationslider is out of the time bound of the image. Currently at least the normal 2d/3d image mappers do so. To reproduce the problem: - load both test data from MITK-Data/3D+t-ITKIO-TestData. - place LinearModel_4D_prop_time_geometry top most - globally initialize - Go to a timestep >= 10 - LinearModel_4D_prop_time_geometry should now dissapear and only LinearModel_4D_arbitrary_time_geometry should be visible because it has the larger time bounds. This is not the case. The last time step of LinearModel_4D_prop_time_geometry is still possible.

Status: As discussed in T25042 mapper should not show images if the time point selected in the Navigationslider is out of the time bound of the image. Currently at least the normal 2d/3d image mappers do so. To reproduce the problem: - load both test data from MITK-Data/3D+t-ITKIO-TestData. - place LinearModel_4D_prop_time_geometry top most - globally initialize - Go to a timestep >= 10 - LinearModel_4D_prop_time_geometry should now dissapear and only LinearModel_4D_arbitrary_time_geometry should be visible because it has the larger time bounds. This is not the case. The last time step of LinearModel_4D_prop_time_geometry is still possible.