playing around with locked / hidden objects based on this topic i came across the following anomaly - or you can call it Bug - at least inconsistency.
or evolutionary leftover ?
grouping
in the following example the two circles are grouped in pairs of overlapping small / big:
Also, moving the groups moves the locked/hidden objects along with the rest of the group. I would intuitively expect hidden and (especially) locked objects to get left behind.
this has been frustrating me for a while too..
Is there no way to hide something in a group and ACTUALLY remain unselected when working on that group? It kinda beats it’s purpose otherwise
When selecting a group, the objects that are hidden also get selected, and this is most likely done by design, so that objects in the group stay in sync when you move them.
But having hidden objects affect trims is at the least not very intuitive, I agree. RH-88141 Grouped hidden objects affect Trim
Dear @Gijs
thanks for digging in.
Did you check the topic i linked at the top … it is about soft-lock, … selecting locked objects…
I am not sure what s the best solution - for both topics.
But maybe a closer look at the status of objects (hidden, locked, grouped, …) is nescessary.
so maybe to keep objects of a group stay together, a group with hidden / locked object should not be able to be moved ?
resulting in an error…
“group could not be moved, because some objects are hidden / locked”
the policy would be, that the weakest status defines the overall behaviour.
currently it s reversed: the most flexible / strongest status defines overall behaviour.
Alternatively, when selecting a group with locked/hidden objects, it could select only the selectable objects with a warning “N locked or hidden objects were not selected”, and then you can choose to manipulate only the selectable objects if desired.
as most users do not care much about feedback, a partial group that does not move will make them more conscious that something is wrong / not how they thought.
advanced users can use sub-selection to move a partial group and get the desired behaviour.
i like the interface - concept: if a command only applies changes to a document, if the input is 100% clear.
this avoids many errors and frustration.
and people will more likely read feedback, if nothing happens.
“oh i can not move it, because one object is looked” is a better didactic experience, then a messed up document because of not being aware of partially moving a group.
When an object that is part of a group and is either hidden individually or on a layer that is hidden, is transformed because a visible member of that group is selected and transformed, that hidden object is shown in the feedback color and shows the transformation.
When the feature of hiding layers in model space only was added in Rhino 8, it looks like the feedback became a bit buggy - the hidden object is still shown during the transformation but does not show that transformation. I put that issue on the list as RH-88314 Group: Only Partial Feedback Hidden Model Layer
-wim
