-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Volume layer opacity does not persist #4650
Comments
The opacity setting is persisted for each dataset (and for each user) independently (regardless of view or tracing mode). At least, this is how it's supposed to be right now if I'm not mistaken. You can change the defaults for a given dataset by editing the dataset in the dashboard. That way, you can set the default for all users who will use the dataset (so, this is only interesting for a multi-user setup). Does this make sense? And does this match the behavior you are experiencing? |
Yes, that makes sense. It doesn't exactly match the behavior I'm experiencing, however. Seems that it's more complicated than what I described in the initial post, so I'll troubleshoot a bit more to find out what triggers the reset. |
OK, the actual issue is as following:
This issue doesn't seem to occur when the dataset has a pre-existing segmentation layer. |
Thank you for the detailed reproduction steps! We'll look into fixing this. |
I could reproduce the bug and trace it's origin to the handling of the |
Ping :) |
Sorry for not replaying. I somehow did not see this issue / mention.
I think that this is possible/ feasible but that would kinda spread the location of where the settings of a layer are saved in the store, which might be confusing. Additionally, if we move the |
After changing the opacity of volume layer in tracing mode (say to 50), if I view a dataset with default segmentation opacity that is different (say 20), then this new opacity (20) is also applied to the tracing mode. Would it be possible to make this setting persistent in tracing mode?
The text was updated successfully, but these errors were encountered: