- All Stories
- Advanced Search
- Transaction Logs
Oct 28 2016
Oct 17 2016
Oct 14 2016
Problem is, the mitk::OpenIGTLinkTrackingDevice has a mitk::IGTLTransformDeviceSource. This works with PLUS and Slicer because they send Transform-Messages for the Tracking Data. But MITK sends TDATA-Messages. Therefore MITK can not connect to MITK because it expects the wrong message type.
Pushed new branch T20004-FixOpenIGTLinkConnection.
Oct 4 2016
Sep 30 2016
Sep 29 2016
Sep 28 2016
Sep 16 2016
We wanted to include the navigation data player as tracking device in the tool storage. This should make the navigation data player available as a tracking device in the tracking tool box.
Sep 15 2016
Pushed new branch T19560-FeaturesMeasurementsPlugin.
Sep 14 2016
Sep 12 2016
Sep 7 2016
Pushed new branch T19946-USVideoDeviceNotWorkingOnLinux.
Sep 6 2016
Sep 2 2016
Aug 31 2016
Aug 19 2016
Aug 17 2016
Aug 16 2016
Aug 10 2016
@kislinsk The refactoring is finished. I thought we merged it into the master, but obviously, as the task is still open, we did not.
Aug 5 2016
Aug 4 2016
Aug 2 2016
Simple reinit on the USIMageStream solves the issue
Correction: the different devices are online on their speciif ports it is just not shown in the GUI
[c877a9]: Merge branch 'bug-19401-PlusCommunicationIntegration'
2015-10-28 17:18:16 Janek Gröhl 
increase message transmission rate from plus to mitk.
The method GetData() is correct. The writing access is caused by c++ specific casting.
[0ff197]: Merge branch 'bug-19338-UpdateGeometryOfUltrasoundimageAfterDepthChang
2015-09-29 11:42:59 Dominique Cheray [1f226f]
Fix Imagegeometrybug for TelemedUltrasoundimage