Commit
This will help preventing conlficts where two armature nodes are added in the tree view. See Issue #13668
- Loading branch information
There are no files selected for viewing
4 comments
on commit a80c5c7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure to understand the reason of this behavior. Can you explain with the "conflict" ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The conflicts was that when importing armatures, a new armature node is created but the old armature node stays the same in the node selection combo-box. Meanwhile, the bones tree view "sees" the new armature node and adds it to the tree view, with the old armature.
This selects automatically the latest armature so this does happen.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is normal that the old armature node stays "current" in the node selection combobox.
However, the fact that the bones tree view "sees" the new armature node is a mistake. It should be fixed in the tree view level. I can look at it if you want.
Nonetheless, if you desire to have the loaded armature being current (like what is done for the volumes), you can look at qSlicerVolumesIO::load
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I'll revert this commit then.
please review comment.