Search Issue Tracker
By Design
Votes
0
Found in
2018.1.0f2
Issue ID
1047096
Regression
No
HideFlags does not work on instantiated prefabs when using a custom class
To reproduce:
1. Open the QA's attached project
2. Open the scene "SampleScene" and play it
3. Go over all selections in the custom "Tools" menu
4. Notice that the 2nd selection "CustomClassNotWorking" does not hide the prefab in the Hierarchy
Expected result: The instantiated prefab is hidden when using the custom class
Actual result: The instantiated prefab is visible in the hierarchy
Reproduced with: 2017.2.3f1, 2017.4.5f1, 2018.1.5f1, 2018.2.0b9, 2018.3.0a1
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
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
- Mouse and Pointer Events are called incorrectly in ScrollView with XRUIInputModule
Resolution Note (2018.3.X):
Setting hideflags on a component does not propagate to the GameObject and other components, this give you fine grained control over the hideflags on each component. The exception is the Transform component which will recursive through the children.