Usecase: I am doing quite the same as in PointBaseRegistration plugin. Two pointsets are registered which leads to a vtkMatrix4x4 that is to be set to a third data node selected afterwards. As in the mentioned plugin I do:
...
mitk::Geometry3D::Pointer movingGeometry = movingPointSet->GetGeometry(0);
movingGeometry->Compose(m_RegistrationMatrix);
movingPointSet->GetTimeSlicedGeometry()->UpdateInformation();
mitk::RenderingManager::GetInstance()->RequestUpdateAll();
Bug: I: In 3D widget the moving pointset is shown as expected but not in 2D views (!?!). So visualization is broken?
II: Then when saving the moved pointset the geometry is not considered. The saved transformed mps file contains the same coordinates as the non transformed one.
You can reproduce this by using the mitk PointBasedRegistration Plugin. MovingPointSet is moved in 3D views but not in 2D views (see attached image).
I used a patched version of 2013.06.0 with OtsuSegmentation bugfix and new MicroServiceIO feature branch.
Best Regards!!!
Ingmar