Pushed new branch T24680-AddPersistenceForUSDevice-PartII.

To the first mentioned point:
In fact, the changing of the cropping when configurating the USVideoDevice does not change the cropping parameters of the image. I left this point open due to a software architectural question: Till now the cropping of the ultrasound image was controlled by the mitkUSImageVideoSource and there was no possibility to configure a probe specific cropping. However, I think it makes sense to have the possibility to configure a probe specific cropping and not an "image specific" cropping. Or what do you think? Should the cropping be controlled by the mitkUSImageVideoSource or by the mitkUSProbe ?

I still cann detect the disturbed ultrasound persistence in the current state of branch T24059-IGTRelease-2018.03 (state: 14.04.2018, 10 am). I am using a Windows 64-Bit build under VisualStudio 2017. How should we proceed?

@seitela and @franza : Reading from xml file should work now (works with the 3 commits from 25.03|28.03|06.04). I haven't had the time for an exhaustive bug-testing of the new functionality. Whenever you find bugs, just let me know. As i mentioned in the last commit: It seems that the used QFileDialog for grapping the needed XML file disturbs the persistence functionality for the configured ultrasound devices. Without QFileDialog everything works fine and the USDevices are stored and restored correctly. But, whenever using the QFileDialog for choosing the stored USVideoDevice xml configuration file, the created USVideoDevice isn't stored/restored by the ultrasound persistence.

Pushed new branch T23729-MakeCheckboxShowToolAxisInTrackingToolBoxClickableAgain.

Ok, I will fix the issue concerning update 3 today and will create the task to update 2 (still not assigned).

Update 1:
The option of displaying the tool projection is implemented.

The use case of MITK as client can be tested by using two MITK instances (one as server, one as client), as well. So, the described use case above seems to be another valid use case that should be tested. Additionally, the reported error does not occur only in the situation described. It occurs in other situations, as well (i.e. sometimes: use virtual tracker --> start and stop tracking --> close MITK --> open MITK --> virtual tracker tool is preset --> change from virtual tracker to another tracker (NDI Aurora or others) --> do not reset preset tools --> try to start tracking --> mentioned error message occurs.)

Update: I will check this task tomorrow (wednesday) and will give a feedback tomorrow, if it is working.

Pushed new branch T24287-SupportTrackedUltrasound-v1-ReleaseIntegration.

Pushed new branch T24287-SupportTrackedUltrasound-v1.

The MITK behavior is no improved. However the optional behavior, mentioned in the task description, is not implemented yet.

Pushed new branch T24037-ImproveMITKBehaviorWhenActiveOpenIGTLinkConnectionInterrupted.

Pushed new branch T24037-ImproveBehaviorWhenActiveOpenIGTLinkConnectionIsInterrupted.

Pushed new branch T24051-LoggingOf_OIGTLDevice_ActiveByDefault.

When using the actual branch "T22595-Masterintegration-2018-01-09" (last pull 15.01.2018) the EchoTrack-Plugin compiles with 144 errors (without the EchoTrack-Plugin everything compiles fine):

With the changes made in branch T23550-ImproveOpenIGTLinkConnection_from_MITK_to_PLUS the connection from MITK to PLUS is working now for the PLUS versions 2.2.0 | 2.6.0 (still not tested with PLUS-version 2.4)

Pushed new branch T23544-Include_OpenIGTLinkPlugin_in_cmake_BuildConfiguration_NavigationModules.

Pushed new branch T23550-ImproveOpenIGTLinkConnection_from_MITK_to_PLUS.

Pushed new branch T23729-AddOptionDisplayNeedleAxisDuringTracking.

Pushed new branch T23708-CrashWhenEditingToolDuringTracking.