Andras Lasso

Thank you! This works well now, I would just ask two last things: 1. When volume rendering a 3 or 4-component volume (especially when `VoxelVectorType: colorRGBA`) then we need to...

I loaded [this RGBA volume](https://1drv.ms/u/c/872af7415c00bfb9/EayjdNbgoSZGno84x5LdPiAB9KIuSXIa1KOmyIQdHRUgeg?e=8IXQFk) by drag-and-drop and then activated volume rendering by drag-and-dropping the image from the subject hierarchy tree to the 3D view and then it did not...

Thank you, I'll check if I can still reproduce the wrong default setting. If not, then it should be good to go.

> Improve the component selection layout Arrange the radiobuttons vertically Change "Index" label to "Component index" I don't see these updates in the latest commit in the .ui file. Could...

Thank you, the layout looks good now. I could still reproduce the black volume by default when drag-and-dropping from Volume Rendering module's subject hierarchy three. It may be because the...

Also, I have these test failueres in my branch that contains this commit: ``` 1> 429 - vtkMRMLVolumePropertyNodeTest1 (Failed) qSlicerVolumeRenderingModule 1> 431 - vtkMRMLVolumePropertyJsonStorageNodeTest1 (Failed) qSlicerVolumeRenderingModule ``` I have some...

I've rebased this on the latest Slicer main version (took care of all the formatting changes) and tested this. RGBA voIume appears correctly now by default, the GUI looks good!...

Done. To fix up an old branch with the new formatting, you can force rebase on upstream, reject all conflicting changes from up upstream, and then run clang-format. I use...

> Remove the style changes. I agree, I wanted to review the changes, but all the whitespace changes made it much more difficult to see the actual changes. If you...

Thanks for the update @riep. I'm refactoring the code to be a bit more consistent with other plugins and will push the proposed changes to this branch soon.