If a layout view, with PrintDisplay on, is intended as a preview of the printed condition then I would make the argument that this is not a ‘feature.’
You have multiple clues as to what the ‘active’ detail is without having to misrepresent it in the Layout.
Clue #1: Increased thickness of detail window outline.
Clue #2: If detail has a name, the upper left of the viewport is changed to reflect the currently active one.
from Rhino 7 help:
‘A layout viewport represents the sheet of paper that will be sent to a printer or a file such as PDF. Layouts can include various views of the model and annotations like title blocks and notes.’
I have had multiple users (myself included!) struggle with why the gradient was not visible. So if this is a feature, there are some UI/UX problems embedded in it.
Why am I posting?
- Accurate approximation of printed result without jumping back and forth between print preview.
- Wasted user time troubleshooting a ‘feature’.
- We often like using rhino models live during internal design reviews. This means zooming between saved model views, but sometimes it is nice to jump to a layout to ground a conversation with multiple related (and curated) views without switching to the generated image/pdf. Keeps a good flow.