Skip to content
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

Loading MRB file breaks linked views #4680

Closed
slicerbot opened this issue Mar 13, 2020 · 4 comments
Closed

Loading MRB file breaks linked views #4680

slicerbot opened this issue Mar 13, 2020 · 4 comments
Assignees
Milestone

Comments

@slicerbot
Copy link
Collaborator

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.

@lassoan lassoan added this to the Slicer 4.11.0 milestone Mar 20, 2020
@sjh26 sjh26 self-assigned this Mar 26, 2020
@lassoan lassoan assigned lassoan and unassigned sjh26 Mar 26, 2020
@ezgimercan
Copy link

I have a similar problem. I usually save MRB files when I am working on a complex visualization. However, if I have double 3D views with different volumes rendered in each, loading the saved MRB file does not setup the same render options. I often end up having both volumes rendered in View1. There is no data loss but the volumes, fiducials and segmentations that are set to be rendered in View2 window are all back in View1 and it defeats the purpose of setting everything nicely and saving an MRB.

@smrolfe
Copy link
Contributor

smrolfe commented Apr 22, 2020

Thanks @ezgimercan. I have experienced this problem also.

@lassoan
Copy link
Contributor

lassoan commented Sep 10, 2021

Not reproducible in Slicer-4.13.0-2021-09-09. Most likely fixed by the large view initialization refactoring.

@lassoan lassoan closed this as completed Sep 10, 2021
@jcfr
Copy link
Member

jcfr commented Sep 14, 2021

Most likely fixed by the large view initialization refactoring.

For future reference, see #5410 (ENH: Simplify view widgets initialization from view nodes)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

6 participants