- User Since
- Aug 1 2016, 11:50 AM (204 w, 5 d)
Fri, Jul 3
Pushed new branch release/T27526-2020-Week-27.
%%% Deleted branch release/T27486-2020-06-19.
Wed, Jul 1
We now have Ubuntu 18.04 and Ubuntu 20.04 clients. Continuous and nightly clients already running. Waiting for another week to activate the Differential clients, as it required code changes and I want to give current Diffs a chance to build that do not already include the fix.
Closing this meta task. Work will be done in targeted tasks.
Mon, Jun 29
Just add it here.
I think I moved and aligned everything into a draft of the official changelog (click on View Draft Version): 2020 Week 25 (Late June).
Fri, Jun 26
Thu, Jun 25
Deleted branch bugfix/T27503-GCC-9.3-Ubuntu-20.04.
Pushed new branch bugfix/T27503-GCC-9.3-Ubuntu-20.04.
Wed, Jun 24
Tue, Jun 23
Separate sections of feature highlights like
Mon, Jun 22
@hettich Why? 🤔
Fri, Jun 19
Pushed new branch release/T27486-2020-06-19.
I can confirm that autocrop in the DataManager context menu is broken and that it probably was never adapted to the LabelSetImage data type: when someone autocrops a segmentation (which is a LabelSetImage since years now even for "binary" segmentations created by the old segmention view), the cropped image should also be a cropped LabelSetImage containing all labels and layers. Other crop strategies like crop to a certain label is subject of the Multilabel Segmentation View context menu, but not of the general DataManager context menu.
Thu, Jun 18
Placeholder for external project updates, minimum CMake version, and Qt version
I went through all Noteworthy tasks of the list above and summarized the ones were I was assigned (we should split it later into API changes and other noteworthy features):
Wed, Jun 17
I think I found a nice solution. Depth peeling is set per renderer, not for the whole application. So it makes sense to activate it only for 3d renders. Side effect: probably speeds up rendering a little bit.
Blocked by the fact that e071-jenkins is not yet reachable from outside.
Tue, Jun 16
Mon, Jun 15
This is also already on the TODO list of the packaging rewrite.
It's depth peeling and it is not solved with VTK 9. I tried to narrow down the issue in a minimum VTK application but I wasn't able to reproduce it. As quite a significant amount of time already was spent here, I will probably reintroduce preferences to disable/enable depth peeling and declare this issue as a known issue.
Fixed a bug where images appeared brighter as they should as soon as the 3d renderer rendered its first image. Only thing missing now is ACVD I guess.
Wed, Jun 10
Fri, Jun 5
Jun 4 2020
Status: Workbench with WorkbenchRelease configuration excluding ACVD/Remeshing starts on Windows. Does not solve T26981: [Segmentation] Multiple Segmentations under one parent node aren't displayed. :/
Pushed new branch feature/T27461-VTK9.
Jun 3 2020
VTK 9 changed core components like vtkCellArray that require a thorough adaption of existing code (including external projects like ACVD).