-
Notifications
You must be signed in to change notification settings - Fork 518
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
Sequence proxy node not updated after reopening scene with stored sequence #7440
Comments
Thanks for reporting, I'll investigate. |
lassoan
added a commit
to lassoan/Slicer
that referenced
this issue
Dec 3, 2023
When a sequence was saved into a scene and then that scene was loaded then browsing did not work. The problem was caused by a typo that set missingItemMode to invalid and thereby disabling copying of sequence content into the proxy node. Fixed the typo, made setting of missingItemMode more robust (if invalid string is found then the mode is not changed just a warning is logged), and added automated tests to capture similar errors in the future. fixes Slicer#7440
lassoan
added a commit
to lassoan/Slicer
that referenced
this issue
Dec 3, 2023
When a sequence was saved into a scene and then that scene was loaded then browsing did not work. The problem was caused by a typo that set missingItemMode to invalid and thereby disabling copying of sequence content into the proxy node. Fixed the typo, made setting of missingItemMode more robust (if invalid string is found then the mode is not changed just a warning is logged), and added automated tests to capture similar errors in the future. fixes Slicer#7440
lassoan
added a commit
to lassoan/Slicer
that referenced
this issue
Dec 3, 2023
When a sequence was saved into a scene and then that scene was loaded then browsing did not work. The problem was caused by a typo that set missingItemMode to invalid and thereby disabling copying of sequence content into the proxy node. Fixed the typo, made setting of missingItemMode more robust (if invalid string is found then the mode is not changed just a warning is logged), and added automated tests to capture similar errors in the future. fixes Slicer#7440
lassoan
added a commit
to lassoan/Slicer
that referenced
this issue
Dec 3, 2023
When a sequence was saved into a scene and then that scene was loaded then browsing did not work. The problem was caused by a typo that set missingItemMode to invalid and thereby disabling copying of sequence content into the proxy node. Fixed the typo, made setting of missingItemMode more robust (if invalid string is found then the mode is not changed just a warning is logged), and added automated tests to capture similar errors in the future. fixes Slicer#7440
lassoan
added a commit
that referenced
this issue
Dec 4, 2023
When a sequence was saved into a scene and then that scene was loaded then browsing did not work. The problem was caused by a typo that set missingItemMode to invalid and thereby disabling copying of sequence content into the proxy node. Fixed the typo, made setting of missingItemMode more robust (if invalid string is found then the mode is not changed just a warning is logged), and added automated tests to capture similar errors in the future. fixes #7440
jcfr
pushed a commit
to jcfr/Slicer
that referenced
this issue
Dec 11, 2023
When a sequence was saved into a scene and then that scene was loaded then browsing did not work. The problem was caused by a typo that set missingItemMode to invalid and thereby disabling copying of sequence content into the proxy node. Fixed the typo, made setting of missingItemMode more robust (if invalid string is found then the mode is not changed just a warning is logged), and added automated tests to capture similar errors in the future. fixes Slicer#7440 (cherry picked from commit 140d58a)
jcfr
pushed a commit
that referenced
this issue
Dec 11, 2023
When a sequence was saved into a scene and then that scene was loaded then browsing did not work. The problem was caused by a typo that set missingItemMode to invalid and thereby disabling copying of sequence content into the proxy node. Fixed the typo, made setting of missingItemMode more robust (if invalid string is found then the mode is not changed just a warning is logged), and added automated tests to capture similar errors in the future. fixes #7440 (cherry picked from commit 140d58a)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
@lassoan
When loading a scene that includes a sequence in Slicer 5.6.0 (I only tested with volume sequence), the proxy node of the sequence node is not updated anymore when playing the sequence.
Steps to reproduce
Environment
The text was updated successfully, but these errors were encountered: