Hi @dalelear , first I appreciate that the new commands start with SubD… now. This is what I’m used to and how I find what I’m looking for. I don’t care how you call it in the end, but creamy/crunchy already is legend
However, I guess this thread is not just about the naming. So let me add some thoughts about functionality. Of course we need to be able to switch between creamy and crunchy, so this is not the question. What I notice is a new behavior and I guess this is what you want to discuss? It is hard to describe these things but I’ll try to explain anyways:
Now there is a sticky* Rhino setting for the SubD display which every new SubD object gets, and there are sticky SubD object display settings (*sticky means a temporary setting which lasts during the current Rhino session / file).
The new SubDDisplay commands work different if SubD Objects are pre-selected: If no SubD object is selected then these commands set or toggle the sticky Rhino SubDDisplay setting which affects new SubD objects. If SubD-objects are selected, then just these objects get or toggle the display setting accordingly. The Rhino settings are not affected. Thus it may happen that you copy a creamy subd object and get the crunchy object and vice versa. This is not intuitive and may cause confusion.
I think it does not need the sticky Rhino setting. One command based on objects selection should work for all scenarios: SubDDisplay(Display=[Toggle Creamy Crunchy] All)
Copies of SubD objects should also copy the current display state.
Just an idea, feel free to ignore or change names to your liking.