I think both is right

1. It is already resolved by work of HackingWeek 2019/2
2. If docu writes something about TabelModel it is wrong/outdates/implementation detail...

Batch is deprecated. Frame Correction is the last opened view.

Clemenst meant Option 2. This is what we have planned.
Cannot tell what @zhangyan meant. I would fix this with option 2.

Pushed new branch T24660-selection_history_inspector.

In T27006#191923, @Sara wrote:

Hi Ralf,
We changed the properties of the data node regarding the T1 map but unsuccessfully.
We always get "Dimension 2 is not in (ItkOutputImageType::ImageDimension)" error.

Just to be sure. The work-arround with the "binary" property (see above) is only for the problem that you weren't able to select the T1 map in the view.
It is not a solution for the Dimension 2 is not in (ItkOutputImageType::ImageDimension) error!

@jsolislemus : Could you provide me your email adresse? Then I will send you the instructions how to transfer data.
Thanks

The problem was caused by the fact that the T1 map has just 2 different pixel values. Therfore it was automatically classified as binary image /mask on loading.

That would be great. Thanks!

In T26998#191725, @kalali wrote:

@floca: This task does not fix T26475 since the QmitkSingleSlotSelectionWidget does not react to node changes itself (see T27000).

Yes you are right. I was inprecise. I already had T26851 in mind because it is on out to do list.

@kalali: If this task is fixed T26475 should be fixed as well, after you introduced the new SelectionWidget to QmitkPropertyTreeView, shouldn't it? Or is it already fixed due to T26381?

Logic is correct. But I would condense it to remove redundancy (see inline comment).

Discussed it offline.

Pushed new branch T26980-Prohibit_dependency_on_autoload_module.

I don't know the status of the branch above as it is dangeling arround for quite some time.

In T25192#164895, @metzger wrote:

NOT READY FOR MASTER!
Already add serialization of properties marked as persistent to the multilabel nrrd writer. Also copied the code from image nrrd file reader to get all properties while reading a nrrd image (not nice but works). But testing was only for one use case. So looking for side effects before merging this commit (6f1b022e7b8d) into master.

rMITK060c74e0e13601d6ccd7653122ce65e2e7fae181 is a proposed fix for the problem.
@neher Do you see any problems?

I have managed to compile now just using cmake cli, when doing the following:

Pushed new branch T26167-Fix_broken_test.

@kompan It is now in the master. ;)

I have the same error on my local Ubuntu VM. But only if configure via CMake command line. If I use the CMake gui and set the same values, then everything works fine.
Generator does not matter I have the problem with make and ninja; with one and multiple jobs.

Sorry for the long delay. Localisers should not be a problem per se. We also have such images in our protocols.

Fixing T26167 was enough for now.

Ok, thanks!

Sooner then later I have to restart on reworking the ChartWidget due to performance problems when transfering data to the java script side. Currently each line is communicated on its own and this communication has an overhead. Paied for every graph line on an update it is a serious performance bump that impacts usability e.g. in the perfusion context.

Oh, great. Thanks for the hint.