@kislinsk mentioned that I might use some feature that is not working with Clang. Actually the only special feature I'm using is qOverload (afaict).

MacOS still fails building MITK (see https://ci.mitk.org/job/MITK/job/Differential/job/macOS%20Mojave/431/console).

Updated D381

Pointed out by @kislinsk in T27095 but as stated before, it belongs to this documentation task not the multi-label one ;)

No issue for 2020, because it is currently not a part of the workbench release.
The problem will be covered by T27196: Rewrite packaging of MITK

@kalali It seems that you work at this task and already have some branch. But the task is not claimed by you. Is it on purpose?

We talked about this task in the group-5 meeting. It turned out that no more foreground pixels are added after the mouse button was released but that it is just a little slow on the test computer and the latest feedback contour wasn't yet calculated when the mouse button was released. So, not really a bug in my opinion. At least nothing new, since the algorithm of the tool did not change.

In T27700#209112, @kislinsk wrote:

Oh... @thomass just told me that there is also T27698: [Segmentation] Segmentation toolbox is never enabled in multi-label segmentation view where it is already resolved... nvm.

Oh... @thomass just told me that there is also T27698: [Segmentation] Segmentation toolbox is never enabled in multi-label segmentation view where it is already resolved... nvm.

Happens only the first time. When I delete all segmentations and then create another new segmentation, the tool widgets in both views are enabled. Might explain why I didn't notice it when doing D312, as I was sure that I tested this before.

• SegmentationInteractor is only used in ML Segmentation. I added the ML context.
• I also added the ML context to the second call of GetToolManager() QmitkSurfaceStampWidget, it was simply forgotten

• MITK_BUILD_OPTIONS for MITK cache vars
• Check why there are documentation errors "lost edge a b" but when I manually "make doc" on the client, it works
• OpenCV somehow seems to trigger Ant errors on Ubuntu only during the first build (problem in Nightlies)
• First time build of MatchPoint triggers many warnings as errors on macOS

Don't ask me what the reason is, that the problem appeared now! But the enabled state was only set at view construction for the ML view. Which lead to disabled tools if you opened it the first time (afterwards a reference image was set in the toolmanager and everything was fine).
Normal segmentation worked arround it by recreating the buttons as soon as data was changed. But I think it is cleaner to let the toolbox widget update the states whenever the toolmanager data has changed.

@thomass : Small workaround until it is fixed: Close the view and open it again. The image and segmentation are autoselected and the tools are active.

@kalali Can you try to retrigger D381? Currently it cannot be reviewed as it is in draft mode.

Deleted branch bugfix/T27436-HideInterpWidgetsInMultilabelSegView.

Notes for the Region Growing 2D tool:

• The tool operates based on the current level window, so changing the level window to optimize the contrast for the ROI should be encouraged
• Moving the mouse up/down is different from left/right. One direction is for level window width, the other direction moves the level window

should work now

I just received an E-Mail that the problem could be related to the data source (some server or network drive) so maybe no MITK issue after all :)

Some additional questions:

• Was your laptop used to build the binaries? If yes, could you check, if yuo can produce the error behavior if you pick a non-mitk-developer maschine and try to load the data there?
• How many frames does the 4D Dicom have? What is its resolution?

Thank you, I wanted to post the discussion result here as well. I will fix this.

The "url" downloads do not work for me. Slack is telling me that "there is a glitch".

I would suggest that at least the plugin feedback in the GoogleDocs and the toplevel-> main page /MITKUserManual should be corrected before the Release. The rest should be corrected soon after.

@kislinsk: should we further investigate this or have a known issue section in the documentation?

In T27669#209010, @thomass wrote:

The log information in the console which Jonas reported doesn't turn up. So the console doesn't show any new information after the reader is selected.
I will ask about the HDD / IO.

The log information in the console which Jonas reported doesn't turn up. So the console doesn't show any new information after the reader is selected.
I will ask about the HDD / IO.

In T27669#209008, @thomass wrote:

she doesn't even get to the logging point. It doesn't show anything, it just stops (She closed the workbench after 10 Minutes).

What do you mean with logging point?

I am not sure if that is related but today one of my cooperation partners reported that she couldn't open an 4D image in MITK (Latest develop installer).
On my laptop it just works fine. On her laptop, however, she doesn't even get to the logging point. It doesn't show anything, it just stops (She closed the workbench after 10 Minutes).
I asked her whether it was an ancient laptop, but no ;)

Discussion result:
As you cannot hook into the Qt connect mechanism, I see no "simple" chance to automatically manage that under the hood. The most pragmatic solution is to simply add a remark to the class (QmitkSingleNodeSelectionWidget) and method (SetAutoSelectNewNodes()) that on should activate this feature *after* connecting the events to ensure already the first autoselect has an effect.

In T27669#208901, @schererj wrote:

It is pretty weird since it even:

suggests 1 3D blocks

Is fixed. but please don't ask when it happened ;).

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Deleted branch hotfix/T25882-CDash-v2.6.