Andras Lasso

> The Slicer launcher executable is built statically, but the CLI executables are not built statically because they have corresponding ResampleScalarVolumeLib.dll and are seemingly depending on the system MSVC runtimes?...

Yes, the promise has been always for backward compatibility only (not for future compatibility) but in practice there has been good compatibility between different MSVC runtimes for many years.

I think the best would be to harmonize the implementation of TypeDisplayName and DefaultNodeNamePrefix, something like this: https://github.com/lassoan/Slicer/commit/3416c1b28c7396d9d3d47a415dca172701a3e7d1 If the change looks good to you then I'll rebase on the...

> Would I still be able to customize the prefix/display name? For example instead of a vtkMRMLMarkupsLineNode utilizing "Line" I would customize it to either "Ruler" or "Caliper" or like...

@jcfr It looks like your concerns have been addressed. Please check and approve if looks good.

We checked and designer is there (comes with the Qt package) but the folder (usr/lib/bin) is wrong (actual location is /usr/bin).

I would find it more intuitive to add an optional `data_file_path` parameter to the existing `nifti_image_read` method. If this new parameter can be passed to the reader, how would you...

Do you mean `nifti_image *nifti_image_read( const char *hname , int read_data, const char *data_file_path=nullptr)` would be considered as backward incompatible? Adding a new method would be OK, too, maybe just...

@cpinter I've refactored the ITK implementation (moved quite a bit of logic from Slicer) and refactored the Slicer implementation (many bugfixes, improvements, performance optimizations, etc.). Please have a look at...

To be consistent with naming of other extensions, such as [SlicerNNUnet](https://github.com/KitwareMedical/SlicerNNUnet), the extension name would be `SlicerNNInteractive`, but there are exceptions to the naming conventions for various reasons, so `nnInteractive-Slicer`...