The current solution was never meant as a user interface but only for saving slice positions in scene files. However, it turned out that it is quite handy to jump to drawn contours with a simple click so we should probably move the list of positions into the segmentation view itself if needed.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jan 12 2022
Suggestion: Open another task for ensuring at least default properties like "visible" that we can then kind of rely on.
We can assume that this is a time-intensive task and a few solutions were already proposed but we do not see how to resolve it completely at the moment with our available resources.
Jan 11 2022
Thank your for the report. I removed all erroneous MITK_DEBUG calls as they should be used rarely anyway.
Deleted branch from rMITK MITK: bugfix/T28910-MITK_DEBUG-Errors.
Pushed new branch to rMITK MITK: bugfix/T28910-MITK_DEBUG-Errors.
Dec 15 2021
Dec 10 2021
Dec 3 2021
Deleted branch from rMITK MITK: release/T28902-2021-Week-48.
Pushed new branch to rMITK MITK: release/T28902-2021-Week-48.
Deleted branch from rMITK MITK: bugfix/T28898-AddMoreThan255Labels.
Pushed new branch to rMITK MITK: bugfix/T28898-AddMoreThan255Labels.
Okay, the fix is very simple as there is an unnecessary check in LabelSet::AddLabel() if the size of the label container is bigger than 255 and then return without any further action. I traced it back to the initial implementation of Sebastian Ordas and I guess it is only there since back then it wasn't clear if label sets should be 8-bit or more. So, a no-brainer to remove the check. All other parts of label set obviously work just fine with more labels.
Dec 1 2021
Can confirm. Tried to load a VTP from a folder called ßè#$§%&!.
Stopping here since it also is in consideration for the new segmentation anyway and AFAIK it wont be a property of the segmentation itself anymore.
Nov 30 2021
I experimented a little with changing the order of filters and using other filters (clean poly data before normal generation, PCA normals estimation) but nothing produced consistent results. So I propose to at least implement a simple flip normals action for the DataManager context menu.
So, this is not a straight forward fix since other interpolations I tested have correct results. Maybe VTK provides a smart filter for determining the outside that can be used.
Thanks!
Deleted branch from rMITK MITK: bugfix/T28882-FixInitialSelectionInPropertiesView.
Pushed new branch to rMITK MITK: bugfix/T28882-FixInitialSelectionInPropertiesView.
Can confirm. To reproduce, it is enough to switch on the Surface.2D.Normals.Draw Normals property and check in any 2-d render window. Meshes generated from segmentations in the Data Manager context-menu have correctly oriented normals in contrast.
Nov 22 2021
Nov 18 2021
Deleted branch from rMITK MITK: bugfix/T28778-fix-rendering-tests.
Deleted branch from rMITK MITK: feature/T28861-SupportVisualStudio2022.
Pushed new branch to rMITK MITK: feature/T28861-SupportVisualStudio2022.
Nov 17 2021
This fix broke some rendering tests regarding scaling. Please fix/revert as soon as possible since these tests have precedence.
Deleted branch from rMITK MITK: feature/T27437-migrate-to-ITK-5.
Deleted branch from rMITK MITK: feature/T27437-ITK-v5.1.
Pushed new branch to rMITK MITK: feature/T27437-ITK-v5.