Hi @enric
I understand the intention behind this, and I agree with it. If I am working on the second-floor plan, I generally don’t want a crossing selection to unexpectedly grab objects that are hidden underneath the slab on another level.
At the same time though, I understand the @badileanu 's point, because selection does not currently seem to behave consistently as a level-based restriction. So should we understand that this selective behaviour is an intentional part of Hidden mode? And if we actually want to select everything, should that require a different display mode, or would it make more sense to give the user control over this and eventually connect it to a selection scope?
There have been numerous times when I click on something while working on one floor and end up selecting an object from another level. Maybe I am wrong about how this currently works, but my impression is that selection itself is not constrained to the active level — Hidden mode simply prevents certain occluded objects from being selected. Please correct me if this is not the case.
This also brings up another question: does every object have a reliable association with the Building/Level it belongs to that VisualARQ can query? I know the level constraints/magnets already establish some relationship between geometry and levels, but I am not sure whether this effectively gives every object an explicit level identity.
If the intention is to let us work cleanly within a specific architectural context, maybe this could evolve into an actual selection scope, independent from visibility:
-
Current Level
-
Visible Levels
-
Current Building
-
Current Space / Room
-
Active Section
-
Entire Model
And possibly a similar scope for snapping as well.
For example, while working on Level 2, I could choose to see Level 1 as a reference but prevent both selection and snapping to it. Or while editing something inside a section, selection could optionally be limited to objects contained in / intersecting that section.
Rhino already has Selection Filters and Named Selections, but what I am thinking about is slightly different: VisualARQ-aware, rule-based selection scopes or selection sets, based on BIM/spatial information rather than only object type or manually saved objects.
This feels to me like it could make architectural modelling considerably cleaner, especially as models become larger.
Does this make sense architecturally with how Levels, Buildings and Spaces currently work internally?
