Andras Lasso

This is getting more and more common. See for example: https://discourse.slicer.org/t/segmentation-issue-invisible-labels/34460/2 It seems that problems come from that researchers use an AI model to compute the segmentation. The inference result...

> For example, functionality specific to Slicer based on vtkITK wouldn't be factored out into the independent MRML project Why vtkITK would be excluded? It contains really useful classes. It...

Fully agree with @pieper in all points. I would just add that a useful aspect of vtkITK is that it connects the ITK filters to the VTK pipeline in a...

- SSL: you can use system SSL or use custom-built Qt that has the right SSL version - Qt connection: update Slicer from latest main version from github - GLEW:...

We would of course be able to read the old files but the current file format has irreparable CSV-incompatibilites: space is used as separator (and therefore space in label name...

Thank you @CPBridge you bring up very good points. For storage of all these additional data that you mentioned we would not need to change the proposed format, just specify...

> the assigned label indexs depends on the order of the segments The most important application of color tables is to prevent this. Voxel values in the exported segmentation are...

Slicer has a global undo/redo mechanism, which can be enabled quite easily (see this branch: https://github.com/lassoan/Slicer/pull/new/enable-global-undo). However, there is one limitation that should be resolved before it gets enabled. Currently,...

@fusentasticus If a feature or fix is critical for you then we can help finding developers (Kitware or other Slicer commercial partners) who can be contracted to work on it.

Why do you need to undo your markups moves so frequently?