Viewport properties in its own window?

Rhino
,
1

Is there any way of moving the viewport properties panel into its own window? I’m not a fan of the way that it disappears whenever objects are selected. Rhino7 for Windows btw.

2 Likes
2

Not currently.

I have logged the request as RH-65676 Have a panel that always shows active viewport properties

1 Like
3

Thanks, it’s been bugging me ever since I upgraded from v5.

4

bumping this request

when working with a renderer in a viewport, it may be hundreds of times a day that we’ll perform whatever series of clicks to get viewport props shown, and then have to use selprev to get back to where we were

even with a button set up to reduce this to a minimum, it’s a lot of unnecessary moving & clicking – at a couple seconds per, not outlandish for it to be on the order of a half hour wasted per week, or more

5

Hi JD -

I don’t disagree, and, I suppose the same could be said for some of the object property pages. When you deselect an object like, e.g. a hatch, and then reselect it, if you’re mostly interested in the main object’s properties, you constantly have to move back to that main page from the more specialized properties tab.

At any rate, and to manage expectations, I see that this YT was set for 8.x back in September 2021 - I really don’t know what that release target would be set to if the developer were to be asked today, but I’m pretty sure this is not going to happen any time soon. If you are using more than 30 minutes every week, I bet you could create a custom plug-in that would save you a lot of time…
-wim

6

yes the idea could be generalized – in principle it is just wanting to be able to pop/duplicate a subset of obj props sup-pages out to its own persistent panel, which only listens to changes in selection of objects of the relevant types

the most general form is probably just the ability to have multiple instances of the current obj props panel, but each with an page type filter, where you can select from a list of icons for all the page types (viewport, edge softening, etc), which ones are allowed to be shown in a given instance of the obj props panel

as far as writing something custom, I could sure make a duplicate of my camera props panel, but this would not get me any of the other viewport properties, and besides that, the whole point of bumping the request is to improve rhino’s own rendering workflow, so that plugins like mine don’t all have to go making their own peculiar ways of doing things