Reading your other task regarding mitkscene files I wonder if it has something to to with attaching the level window property to the BaseData property list instead of the DataNode property list. In principle, the level window should be attached to the latter one as it is an "appearance" property and not something instrinsic to the data. A few years ago we changed the way properties are queried and when a property is not present in a DataNode property list, the Base Data property list is queried as fallback. Maybe it is not fully functional for level windows as it could be that the code somehow relies on / assumes that the properties are located in the DataNode property list.

Not sure if I fully understand what is going on here but the difference is that in your first example you have DataNode properties and in your second example you have BaseData properties, right? Let's talk about it in our group 5 meeting today. :)

@a178n I added cpp-httplib as dependency to MITK in the branch mentioned above so you can easily experiment with it. For details, see rMITKf88e3d05aeb0: Add cpp-httplib as optional dependency.

Pushed new branch to rMITK MITK: feature/T29421-httplib.

After a meeting with Ralf and Stefan (30.11.2022), the header-only library cpp-httplib (GitHub: https://github.com/yhirose/cpp-httplib), was chosen as a promising alternative. The library seems the most popular in the GitHub community compared to Pistache, the second favourite library from the list.
Hands-on efforts to build server and client calls will be undertaken to test further suitability.

The literature survey searching for alternatives is summarized here: https://hub.dkfz.de/s/qsEgaWybwiWcfYN

Should be tackled as soon as T29206: [SEG] Implement a Qt model for LabelSets for MVC patterns is done.

Adding a data node reset-geometry-action was a first step and enough to tackle this issue. If there are more requirements for some "intelligence", new tasks need to be opened.

Render window specific visibility has to be covered, as mentioned in D756#26848. This will be done in T29403: [mxn multi widget] Concept for crosshair data type.

This task is invalid; related work will be continued in T29297: [mxn multi widget] Optimize data accessibility inside render windows.

Also regard T25445: MultiLabel segmentation mapper is very slow

This issue should also be regarded if T26959: [Segmentation] Newly created LabelSet segmentation is not displayed as "outline binary" is done.

Now with the preferences moved to micro services, we can move the selection widget T29027 and then use them also here.