I never use the viewport tabs to switch views, so I never noticed this. But some of the people here pointed out that if you use the DisplayObjectMode in one view, then switch to another view using the tabs, that object’s display mode goes back to the viewport mode. Does this make sense? If a user intentionally sets an object to display differently than the viewport display mode, shouldn’t that choice “stick” between viewports? It does if I just type the viewport name to switch views.
I know there are some scripts from 2014 to accomplish this, but it seems to me that there should be at least an option to apply ObjectDisplayMode settings to all viewports. I also noticed that there are no methods in the Rhino-Python methods list for dealing with ObjectDisplayModes.
There’s probably a reason it doesn’t do this now, that’s why I’m suggesting an option so it’s a bit more useful for everyone.
Yes, but it could have an option to apply to all viewports… something that has been missing since its inception. It’s scriptable, so I don’t think it should be a huge problem to integrate that functionality natively.
@DanBayn - here are my versions, revised since 2014 just in case.
What would be very helpful is to copy the per object assignment from one VP to another VP of choice.
What I often do, is setup a nice configuration in one VP, but then would like to have the same in another.
All the scripts i found work for new assignments, but not to copy an existing assignment to another VP.
have I missed that somehow?
Concerning the problem Jeff LaSor posted in the YT link, I think this could be an idea:
For each VP, have a switch to “override” : use current display mode <> use custom assignment
Custom assignment would however store a seperate assignment table for each VP where anything has been modified, meaning you could have “named ObjectDisplayModes” that are stored and can be assigned to the “override slot” of any VP
