Selecting objects in detail view and hidden view mode

[djhg]

Thanks Alfonso. But it’s not the selection colour I’d like to change. It’s the display colour of the background of an active detail in Hidden View mode - from white to something of a more neutral luminance. But I’d like the detail to print its background in the way it currently does.

[enric (Enric Marquès)]

Hi @djhg,

I don’t understand your problem, or more specifically, why there is a problem only with the “Hidden” display mode. You can change both the background color (in the Display mode options) and the selection color work (in the Appearance options). If you don’t like yellow selection color on a white background, then you can change them.

What is not supported by Rhino is to change the background color for a display mode only when it is an active detail.

In my opinion, yellow is not a suitable selection color. I always change it to blue, like Windows and all major operating systems use. I find it more consistent to me that layer selection in the layers panel and object selection in the viewport use the same color. But again, this is just my personal preference.

Enric

[djhg]

Thanks Enric

@enric

why there is a problem only with the “Hidden” display mode.

Because it’s the only View Mode I use regularly that has a background which turns to white from grey when a detail is active.

@enric

You can change both the background color (in the Display mode options)

If I do change it to - say - a blue grey, can I set it to print as a) white or b) alpha though it displays blue grey in an active detail?

[enric (Enric Marquès)]

Hi @djhg,

Rhino doesn’t use the background color for printing for any display mode, unless you turn on this setting (which by default is off):

Enric

[djhg]

Thanks Enric. Great. I’ll actually change the background to a blue grey and keep the seleciton colour at yellow. I’m used to that from AutoCad and all the way back to Imagine on the Amiga.

[djhg]

From my post a few posts earlier:

@djhg

It seems that if any object, certainly a Va object, is cut via a plan section from the levels panel, a crossing selection will only select it (apparently, based on the absence of highlighting the target object) if the crossing section goes through two edges of the object. I’m not sure lassoing an entire object is reliable either. I haven’t noticed these issues in other view modes. This unexpected behaviour (if intended) and woukd be good know, because otherwise it leads to the perception that the detail is inactive or print display is on or the selection filter is active, and attempting to remedy any if those situations leads to cascading confusion.

I’ve created a new post for this, because I can’t reproduce it in a hidden display mode detail, but I can in a wireframe view mode:

Selection Limitations in Sectioned Detail View

The gif below shows that in this sectioned wireframe display mode view, a lasso selection must go through a vertice in an object (in this case a Vastair, Floating style) in order to select it. Not sure if this is intended, or even has always been the case. It’s new to me. This detail is on page 4 of my most recently uploaded file. [SelectionLimitationInSectionedDetailView]

[alfmelbev (Alfonso Melero Beviá)]

Hi @djhg, we have just released a new version of VisualARQ (2.12.5) which fixes this error you reported about selecting objects in a detail view if PrintDisplay is on with the “Hidden” display mode.

You can check here the news of the new version: VisualARQ 2 - Version 2.12.5 released

You can download this new version here .

Enjoy!

[djhg]

Bravo! Thankyou.

[djhg]

However, it takes so long for an object to show as selected that I’d forgotten this problem had been corrected. (I’ve got the fastest processor available for a laptop as of Christmas.) Actually that’s just some of the time. A lot of the time it doesn’t work at all. I don’t think the problem is fixed. At least not for the type of projects I do. I know it would be good to upload one to you, but I’m afraid that’s just not as possible as it’s required for this troubleshooting. It’s difficult to imagine that it works for the dev team but seldom for me.

[fsalla (Francesc Salla)]

Hi @djhg we have tried to reproduce this situation with different models and it works fine in all of them. Please share any file where we can reproduce this issue.