After loading data, render state is not yet consistent

[scottwittenburg]

The video below shows loading the yeast_mito-T9-filtered.nrrd data set. Notice how selecting the tab for the color/opacity map at component index 1 results in a change to the image. Simply opening the editor for these properties, but not changing any of them, should not cause the rendering to change.

[thewtex]

The Gaussian in the transfer function widget is likely only applied to the first component that is selected -- we will have to cycle through all the components and apply the initial Gaussian as the piecewise function for each component in the rendering initialization logic.

[scottwittenburg]

Thanks @thewtex ⛑ I did try to do something like that, but I must not have found the right point in the rendering setup, as it didn't fix the problem. I added some code to loop through all the components and do what you suggested at the bottom of the createTransferFunctionWidget.js module, but that seems not to be the right place. I'll keep after it.

[github-actions[bot]]

:tada: This issue has been resolved in version 11.0.0 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: