Restictions on child objects affects parent duplications #38830

New Issue

Victor Remolina · 2014-02-25T13:12:33+01:00

Victor Remolina commented

2014-02-25 13:12:33 +01:00

System Information
platform: b'Linux:64bit'

Blender Version
version 2.69 (sub 11), branch b'master', commit date b'2014-02-20' b'05:32', hash b'10f4c62', b'Release'
build date: b'2014-02-20', b'06:40:09'
build cflags: b'-DWITH_FREESTYLE -pipe -fPIC -funsigned-char -fno-strict-aliasing -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -fopenmp -DNDEBUG -O2 -msse -msse2 -DWITH_MOD_FLUID -DWITH_MOD_OCEANSIM -D__LITTLE_ENDIAN__ -DWITH_AUDASPACE -DWITH_AVI -DWITH_OPENNL -DWITH_BOOL_COMPAT -DHAVE_STDBOOL_H'
build cxxflags: b'-pipe -fPIC -funsigned-char -fno-strict-aliasing -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -fopenmp -fpermissive -D__STDC_CONSTANT_MACROS -DNDEBUG -O2 -msse -msse2 -DWITH_MOD_FLUID -DWITH_MOD_OCEANSIM -D__LITTLE_ENDIAN__ -DWITH_AUDASPACE -DWITH_AVI -DWITH_OPENNL -DWITH_BOOL_COMPAT -DHAVE_STDBOOL_H'
build linkflags: b'-lrt'
build system: b'SCons'

Short description of error

Hi,

I want to report an undesirable behavior takes place in all versions of Blender.

When you create a bone or hierarchy and attact some objects to it, making children objects, when you disable the "Restrict viewport visibility" on the Outliner panel for one of those objects it is always excluded from any hierarchy selection of his parent. It also makes the hidden object dissapear in the Outlainer panelin "selected" mode although the Parent is selected.

I think the desired behavior of the "Restrict viewport visibility" might afect only to the display of the object, not to the hierarchy selection, just the way the "Restrict rendering" flag works.

PLease find attached a prepared file for checking

Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps

1- Create a parent with chil objects
2- Disable "Restrict viewport visibility" (eye icon) in the outliner panel for one of the Child objects
3- Select the parent with all the hierarchy, by:
- > presing Ctrl + Shift + Parent object in Outliner panel

OR

  - > Right click on the Parent Object and click on "Select Hierarchy" option

4- You can see the object "Restricted on view" isn't selected
5- Duplicate the object, you will check the hidden child object was no included in the duplication

Repeat al steeps by disabling the "Restrict for rendering" option (Camera icon)... you will see the hidden object is selected and including in the duplication od the parent.

Personal opinion just for comment, restrincting view of an object must not affect working with the parent as long as the hidden object stay in this condition after the duplication or selection... on the other hand "restricting selection" is the way to exclude the object to continue working with it if is a desired way to do it. From my part I would rather on dupliucate the entire object (regardless the temporal restrictions) and deleted non desired child objects by my own.

bug_no_select_hidden_view_childs.blend

Thanks a lot
Victor

**System Information** platform: b'Linux:64bit' **Blender Version** version 2.69 (sub 11), branch b'master', commit date b'2014-02-20' b'05:32', hash b'10f4c62', b'Release' build date: b'2014-02-20', b'06:40:09' build cflags: b'-DWITH_FREESTYLE -pipe -fPIC -funsigned-char -fno-strict-aliasing -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -fopenmp -DNDEBUG -O2 -msse -msse2 -DWITH_MOD_FLUID -DWITH_MOD_OCEANSIM -D__LITTLE_ENDIAN__ -DWITH_AUDASPACE -DWITH_AVI -DWITH_OPENNL -DWITH_BOOL_COMPAT -DHAVE_STDBOOL_H' build cxxflags: b'-pipe -fPIC -funsigned-char -fno-strict-aliasing -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -fopenmp -fpermissive -D__STDC_CONSTANT_MACROS -DNDEBUG -O2 -msse -msse2 -DWITH_MOD_FLUID -DWITH_MOD_OCEANSIM -D__LITTLE_ENDIAN__ -DWITH_AUDASPACE -DWITH_AVI -DWITH_OPENNL -DWITH_BOOL_COMPAT -DHAVE_STDBOOL_H' build linkflags: b'-lrt' build system: b'SCons' **Short description of error** Hi, I want to report an undesirable behavior takes place in all versions of Blender. When you create a bone or hierarchy and attact some objects to it, making children objects, when you disable the "Restrict viewport visibility" on the Outliner panel for one of those objects it is always excluded from any hierarchy selection of his parent. It also makes the hidden object dissapear in the Outlainer panelin "selected" mode although the Parent is selected. I think the desired behavior of the "Restrict viewport visibility" might afect only to the display of the object, not to the hierarchy selection, just the way the "Restrict rendering" flag works. PLease find attached a prepared file for checking **Exact steps for others to reproduce the error** Based on a (as simple as possible) attached .blend file with minimum amount of steps 1- Create a parent with chil objects 2- Disable "Restrict viewport visibility" (eye icon) in the outliner panel for one of the Child objects 3- Select the parent with all the hierarchy, by: - > presing Ctrl + Shift + Parent object in Outliner panel ``` OR ``` - > Right click on the Parent Object and click on "Select Hierarchy" option 4- You can see the object "Restricted on view" isn't selected 5- Duplicate the object, you will check the hidden child object was no included in the duplication Repeat al steeps by disabling the "Restrict for rendering" option (Camera icon)... you will see the hidden object is selected and including in the duplication od the parent. Personal opinion just for comment, restrincting view of an object must not affect working with the parent as long as the hidden object stay in this condition after the duplication or selection... on the other hand "restricting selection" is the way to exclude the object to continue working with it if is a desired way to do it. From my part I would rather on dupliucate the entire object (regardless the temporal restrictions) and deleted non desired child objects by my own. [bug_no_select_hidden_view_childs.blend](https://archive.blender.org/developer/F78908/bug_no_select_hidden_view_childs.blend) Thanks a lot Victor

Victor Remolina commented

2014-02-25 13:12:33 +01:00

Changed status to: 'Open'

Victor Remolina commented

2014-02-25 13:12:33 +01:00

Added subscriber: @tharkos

Brecht Van Lommel commented

2014-02-25 18:10:15 +01:00

Added subscribers: @ideasman42, @brecht

Brecht Van Lommel commented

2014-02-25 18:10:15 +01:00

I can see that in this case it would be more convenient to select the hidden child object, however I don't think we should change the behavior. The select hierarchy tool could be changed but the duplicate object operator should work as it does now.

The rule is now that if an object is hidden in the 3D viewport, you can't edit it in the 3D viewport. I think we need to stick to that rule, it prevents nasty surprises where you might accidentally edit or delete objects without knowing. In the outliner you can select it and e.g. delete it, since it is visible there, but there is no duplicate tool there. Ideally there would be one there, I think that would be the better solution, though extending the outliner is more a to do item than a bug.

@ideasman42, do you agree with this?

I can see that in this case it would be more convenient to select the hidden child object, however I don't think we should change the behavior. The select hierarchy tool could be changed but the duplicate object operator should work as it does now. The rule is now that if an object is hidden in the 3D viewport, you can't edit it in the 3D viewport. I think we need to stick to that rule, it prevents nasty surprises where you might accidentally edit or delete objects without knowing. In the outliner you can select it and e.g. delete it, since it is visible there, but there is no duplicate tool there. Ideally there would be one there, I think that would be the better solution, though extending the outliner is more a to do item than a bug. @ideasman42, do you agree with this?

Victor Remolina commented

2014-02-25 18:59:47 +01:00

Hi Campbell,

I agree about it's not a bug and now, from the point of view of the 3D view it takes sense to work in this way.

Problem comes because the Outliner Panel in "Selected" mode is not displaying the reality of a hierarchy at this time unlike the other modes. The "restricted view" child objects are not shown when you select a Parent object so you are no aware about the hidding childs objects are going to be avoided on next 3D view manipulation.

Imagine you have a Troll with a hat into a battle, if you "restricted view" the hat of that Troll... the hat will disappear from you outliner in Selected mode (unlike if you "Restrict render"). Now if you want to use or show the hat, you will have to go to the outliner in Scene mode and find your happy Troll into a big list

I find working whith files with a lot of objects is really usefull to use two Outliner panels art the same time, one in groups mode for big manipulations and other one in Selected mode tho change the specific rigs content... really useful on working making crowds :)

Sorry for the big text, at the end... do you think I the Outline behavour in Selected mode its a bug? I can open another bug just for it if you find it correct.

Thanks a lot again
Victor

Hi Campbell, I agree about it's not a bug and now, from the point of view of the 3D view it takes sense to work in this way. Problem comes because the Outliner Panel in "Selected" mode is not displaying the reality of a hierarchy at this time unlike the other modes. The "restricted view" child objects are not shown when you select a Parent object so you are no aware about the hidding childs objects are going to be avoided on next 3D view manipulation. Imagine you have a Troll with a hat into a battle, if you "restricted view" the hat of that Troll... the hat will disappear from you outliner in Selected mode (unlike if you "Restrict render"). Now if you want to use or show the hat, you will have to go to the outliner in Scene mode and find your happy Troll into a big list I find working whith files with a lot of objects is really usefull to use two Outliner panels art the same time, one in groups mode for big manipulations and other one in Selected mode tho change the specific rigs content... really useful on working making crowds :) Sorry for the big text, at the end... do you think I the Outline behavour in Selected mode its a bug? I can open another bug just for it if you find it correct. Thanks a lot again Victor

Campbell Barton commented

2014-02-26 01:57:24 +01:00

The issue is the outliner is activating scene selection, so it must respect hidden state.

Maybe there can be some way to alleviate annoyance...

Report that one or more of the objects is hidden when doing a recursive select (no popup, just message in the header)
Add the ability to recursive unhide from the outliner.

@brecht, yep agree we shouldn't change this for now and is more of a TODO.

The issue is the outliner is activating scene selection, so it must respect hidden state. Maybe there can be some way to alleviate annoyance... - Report that one or more of the objects is hidden when doing a recursive select (no popup, just message in the header) - Add the ability to recursive unhide from the outliner. @brecht, yep agree we shouldn't change this for now and is more of a TODO.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Restictions on child objects affects parent duplications #38830