Closed rbumm closed 1 year ago
These errors have always been there, but only appeared in the error log, not in the console. We unified logging to make it easier to see all errors resulting from a command (not just at Python level but from VTK, Qt, CTK as well), therefore these errors now show up in the console.
They seem harmless, but we should eventually fix them. If you specify objectName for all the Qt layouts you create and the layout error is in Slicer core. We would need to add logging of the object name to ctkSliderWidget::setSingleStep() and then we'll hopefully see where the error is coming from exactly.
Including
self.layout.objectName = "Lung CT Segmenter layout"
and they are still there in their initial form, so probably they are generated elsewhere.
These warnings occur frequently in Lung CT Segmenter and after adapting it to 3D Slicer 5.2.1
@lassoan May they be related to SegmentEditorWidget calls and can they be avoided?