I accidentally uploaded the segmentation. This is the raw data. The problem occurs with both.

Pushed new branch T25604-Switch-between-different-render-windows.

Pushed new branch T24161-Common-interface-for-multi-widget.

Pushed new branch T24771-Integration.

The branch is checked into the master and tested with the image statistics plugin.
The complete API of QmitkChartWidget is not tested in detail, for example more than one labels with different chart type...

The tutorial ("Welcome screen") has light theme and the old icons. This might be quite confusing for new users.

Typical candidate is unnecessary generation of data becasuse timestamps are not utilized to their fullest in a mapper.

Whoever will work on this: We currently are based on CMake 3.10. With CMake 3.13 there is a new standard way of setting the debug environment (e.g. PATH=...) for visual studio projects.

In T24770#169648, @kislinsk wrote:

Threading issue? Making WeakPointer thread-safe?

That wouldn't contradict the racing condition assumption. Isn't the WeakPointer thread-safe already?

This really is an issue on Ubuntu at the moment. Works with installed version of the Workbench, but requires the system-version of Qt5PrintSupport to be installed with the built version of the Workbench. Then, the message mentioned above shows up and every start afterwards works.

Is this connected to (or even the same problem as in) T23590?

Threading issue? Making WeakPointer thread-safe?

I like it.

also tested on Linux

warnings as errors on by default: New CMake option WARNINGS_NO_ERRORS

You are right, Plot.ly has something similar which is easy to activate.

I do not think, that the subchart feature is a blocker or even critical. It was very easy to implement with C3 and I personally liked the idea as described above. I assume there is something to achieve that in plotly as well? I'd be happy to discuss this with you in person.

@steint great work. That already looks really good, thanks!!
Personally, I am no fan of the subchart feature, but see the rationale of @kleina. It is possible without great effort in plotly?

The idea behind that feature was, that it should be obvious to the user, that he is only looking at a part of the data. A zoomed view can lead to misinterpretation if the user is not aware of it. At least that is what I thought when I added that feature.

Do we need the subchart feature? Maybe the interactive zoom option with plotly is sufficient?

Thanks, i will keep an eye on the file size and test it with MP4s ;) hope you like the moving images.

FYI: Instead of GIFs you can also use MP4s in Phabricator, which tend to be much smaller in file size while having a decent framerate.

Pushed new branch T23758-New-multi-widget-editor.

First draft has been proven to be working (also with RenderWindowManager, see T25603) and merged into T23758. This task will be closed now and other subtasks will be created from the meta task.