Curious why the Scene Graph Tree uses toggles for visibility, selectability etc, but the Collection tree uses radio buttons for same?
IMO the UX is far stronger with toggles, especially when you want to do quick on/off to compare things, for example. Also radio buttons take up more real estate. However, perhaps I'm missing some advantage of radio buttons?
Also unfortunate that there is no "Deselect" for Collections, that would be super useful, though maybe I'm missing it. Basically the "select primitives" column should be toggles too. IMO of course!
The reason for the different UI is performance. Showing toggles for the Collection API section would requires maintaining a list of every prim in every collection, and comparing that list of (possibly tens of thousands) of prims against the list of currently selected (or visible, or activated) prims so we could show the correct state of the check boxes. And we'd have to redo this calculation every time the LOP nodes recook.
Also, often we'd be in a state where some of the prims in the collection would be in state A, and some in state B, leading us to want both the "set all on" and "set all off" UI anyway - though showing the "current state" accurately is reason enough to want this UI to change IMO.
Maybe not a satisfactory reason, but you did phrase this in the form of a question
Indeed it was just a question Obviously it's workable, and performance seems like a good reason especially at scale as you mention.
I haven't really used Solaris "for real" until now, and my goodness it has improved radically since I last took a look at it over 3 years go. Congrats to you and the team for this becoming so powerful and easy to use!
