Search Issue Tracker
By Design
Votes
2
Found in
4.5.2f1
Issue ID
623951
Regression
No
[SelectionBase] attribute on parent GameObject does nothing when prefab child exists
To reproduce:
1) Make two gameObjects and give them a child which you can click in sceneview easily, for example, Sphere
2) Make one of those Spheres a prefab
3) Create a script and add SelectionBase attribute
4) Attach script to each parent
5) Select each object from scene view. When object with no prefab is selected, the parent highlights in hierarchy. When object with child prefab is selected, the child is highlighted in hierarchy
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mistakes in multiple Particle System Components pop-up
- Hovering on the Particle System Controls shows an offset tooltip with the overlay window name
- Inconsistent UI hover colour with poor contrast in VFX Graph window
- Lights with Cookies generate Cookie Atlas and increase Memory usage every time when Play mode is entered
- Crash on mono_traverse_object_internal when exiting Play mode on a specific project
Xarbrough
Mar 10, 2018 01:25
Yea, why is this by design? Prefab roots are generally prioritized, that's fine, but the SelectionBase should let me specify exactly which object is selected when searching up the hierarchy. I'd even say this is the most common use-case, because the things we select in the scene view are typically meshes, which are close to the deepest level of the hierarchy, but often we want other components to be selected at a higher grouping level, hence the SelectionBase attribute should also select parent GameObjects of prefabs.
Stardog
Nov 04, 2016 19:41
This needs fixed. It's shouldn't be "by design".
yuewahchan
Jun 05, 2015 10:36
It is broken in 4.6.5f1