Clipping planes still too painful. Will it get better before V6 launch?

[SamPage]

@fraguada

For hatches, wouldn’t this be more ‘Rhino’ if an object had a hatch attribute by layer, by parent, or by object? VisualARQ has had this for some time: Documentation tools - VisualARQ

I think you are right, it would be more useful for that to be an object / layer property than a clipping plane property.

Hopefully not to getting too far off topic, I have often been intrigued by VisualARQ; but I’m not sure I would get great fit for the work I do. While film / TV / theater drafting share a lot of conventions with architecture, we have a lot of unique situations (most of our walls are single sided, many have to move, that kind of thing), which I’m not sure VisualARQ can handle. Native clipping planes in Rhino are quite flexible, and for the most part work for what I need, I just wish they worked better.

@pascal

[I]n your image you have a layout (‘Sht_02’) that opens up to show details (‘Plan’ in this case) and from the details you can expand to see the clipping planes that are active, or could be active, in the detail, am I reading that right?

My thought was just showing clipping planes that are active, which would I think make seeing what clipping planes are affecting the detail / viewport easier instead of looking over a giant, mostly empty list. The could be active clipping planes (which I would think would be all clipping planes) would in my mock up be on the right hand pane.

One handy thing about the available clipping plane list on the right of my mock-up is that it would also let you easily spot orphaned clipping planes (which I admit with my carelessness I often end up with several).

@pascal

LayoutManager panel with all of this and maybe other stuff like scale other detail and layout properties

(I’ve had this fantasy before Wish V6: Better Layout Management - #2 by SamPage )