| floca | |
| Oct 10 2022, 5:33 PM |
| F2577461: grafik.png | |
| Oct 10 2022, 5:33 PM |
if data is loaded in the "wrong" order, the segmentationview ends up in invalid states (e.g. labels are not shown, or wrong labels).
How to reproduce:
| rMITK MITK | |||
| Restricted Differential Revision | rMITK4ad97a5dfe79 Rename On prefix from methods that are no slots | ||
| Restricted Differential Revision | rMITK4bd91c146951 Fix selection handling of Segmentation View | ||
| Restricted Differential Revision | rMITK47a8b41133bc Fix unused parameter warning | ||
| Restricted Differential Revision | rMITK6c3ea29d3d69 Fix a potentially wrong segmentation selection | ||
| Restricted Differential Revision | rMITK035c6062c0f4 Refactor self-call check per instance | ||
| Restricted Differential Revision | rMITK94c627cbe744 Show interpolation warning only with multiple labels | ||
| Restricted Differential Revision | rMITK03cb15e10697 Fix invalid states of Segmentation View for certain selection scenarios | ||
Looking at the code I noticed that there are quite a few possibilities to trigger invalid states which all have in common, that the selection of the reference image or working image are handled separately while neglecting the overall selection situation. I will refactor the two OnSelection handlers into a common one that can assess the overall situation without duplicating logic. This will also fix a few other bugs and will also enable to use the layer, label, and label set widgets when only a working image is selected. This is totally fine as all actions these widgets provide are independent from a reference image.