The Shadows checkbox will only be enabled if the Display Mode’s settings have enabled Shadows (Properties > Display Modes > Shadows > …)
…but perhaps I should be reading a nuance into your observation that I’m not
Yes. That setting (on/off) should be accessible as it is in Windows for the various display modes from the panel… Shouldn’t have to drill down into Preferences (not Properties, this is not Windows ) > Display Modes > ModeName > Shadows to set it on or off.
That setting (on/off) should be accessible as it is in Windows for the various display modes
Sorry, now I think I’m really confused. If Shaded Viewports have shadows disabled; and if (for the sake of discussion) the viewport in question has a tick-box for Shadows that can be enabled/disabled, would you expect it to enabled/disable all Shaded viewports, or just this shaded viewport?
Whoops! Good catch…I don’t know how that got typed
Well, in Windows Rhino anyway, each display mode has a unique name - you can’t have two with the same name. Doesn’t matter if it’s based on shaded, rendered, technical or whatever… I assumed that the display panel in Mac Rhino showed the currently set display mode NAME in the active viewport - as does Windows Rhino - is that not the case?
If so, I expect the panel setting to behave like the Windows setting does - turn shadows on or off for the particular named display mode that is current in the active viewport.
There seems to be a couple of bugs here…this needs more investigation. I just created a new Custom Rendered display mode from the Standard display mode. I named this “Rendered” (not advisable, I know). I was able to switch to “Rendered” (the custom one) in my active viewport and do enable/disable Shadows from the Display panel (inspector). Ok…sort of weird, but not overly so. Then I deleted the “Rendered” display mode and switched by active viewport back to the Standard Rendered display mode (with shadows disabled). Then I was able to enable/disable shadows from the Display inspector. Catch that last part…?
Then I went back to repeat this bug and I could not. Not a good sign
Display modes do not follow the “immutable” Standard template pattern that @marlin (and I, for that matter) prefer. Tweaking a property like enable/disable Shadows should not require creating a copy…hence the Revert to default values option. But there are definitely a couple bugs going on here…I just need to repeat them. Perhaps it’s as simple as your original contention however…
What I want is for the shadows option (checkmark) to be active in the inspector for ALL display modes where it is applicable (i.e. all non-wireframe modes), regardless of whether they are the originally supplied default modes, copies of those modes, modified custom modes, or whatever… I hope that’s clear…
I agree it can be a wild ride finding functions spread over many places referencing similar functions. I too have had problems with shadow being in multiple places so not at first obvious what does what.