Does this fix address Lauren's request? The solution appears to be the reverse of the original request.

The bug said Lauren wanted her node subclass not to show in a node selector for general models. To maintain this capability with the proposed fix, every node selector in Slicer that is configured to select models would have to be configured to not select subclasses. As more node selectors are added to Slicer, we'll have to configure them not to select fibers.

What if there are two subclasses of models and you want to only show one of the subclasses in the general model list?

I think perhaps, Lauren wants to "hide" the fiber nodes from the selectors in general (which there is an ivar (HideFromEditors) to do this), and then enable particular node selectors to view these "hidden" fiber nodes whenever fiber nodes should be selected.

Hi Lauren,

What's the status of this bug? Did the fix address your problem? Thanks! -K.

I went through this apparent reversal of the desired effect with Alex via email, and I believe it was fixed. I haven't had time to work on slicer3 and test yet, I will inform when I know for sure that it works. Thank you!

Hi Katie,

Finally I am testing this. It does not work as expected for me. The fiber bundles are children of vtkMRMLModelNode, and they still show up on the menus in the Models GUI. To prevent this, those menus (in the Models module) would have to not show child classes. I think the fix was implemented as a menu option but not selected yet in Models.

Also, I suspect another bug. The effect is not as expected when I load the vtk model (fiber bundle) in the Slicer3/Modules/Tractography/Testing/TestData directory. I load it using the Tractography->Tractography->Load interface. It is displayed as a model (blue polylines always visible) and as a fiber bundle (as lines/tubes/glyphs when requested by my Tractography->Tractography interface). Strangely, changing model properties in the Models module affects the tubes or glyphs rather than the ever-present blue line (perhaps another bug with all these models having the same name, although the tubes/glyphs are supposed to be hidden from editors).

I realize that resolving this by the current method is asking the Models GUI to ignore its child classes. Is it likely that the Models module will want to pay attention to other child classes in the future? For now at least it would be great if the ignore child classes flag is set in the Models selectors.

I just reread Jim Miller's comments above. Currently I am not hiding the fiber bundles from editors, just the "fake models" used to display them. The idea is that all of my modules will want to see the fiber bundles so they shouldn't be hidden... Or, they should be hidden from everything not specifically trying to select a fiber bundle. However this isn't an option now?