Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
1
Found in
4.0.0f7
Issue ID
509928
Regression
No
Inconsistent / confusing open and close of components of same type
Inconsistent / confusing open and close of components of same type.
In the sample scene, look at the TestObj. It has 3 identical components, which for the sake of showing what's happening have an OnDrawGizmos event.
Make sure that all the scripts are 'open' (not minimized in the list of components in the inspector). Now close 1 of the 'TestDrawGizmos' components. It will minimize, and all the gizmos will disappear from the scene. This is indicative that all scripts of the same type have been closed in the inspector - if you click on the Main Camera and then back on TestObj, you'll see that they're now all showing as minimized. The same thing happens if you open one of the minimized scripts - they all get un-minimized, you can see the 3 gizmos, you just don't see any change in the inspector.
Ideally, minimizing one instance of a script wouldn't minimize every copy of that script everywhere. This is especially true when using gizmos - I might want to be able to hide one or two to be able to see/access other gizmos more easily.
I can understand why this might have been done purposefully (that's how the Gizmos dropdown in the scene view works, by minimizing all copies of the script in parallel), but as it is now it's very confusing behaviour.
Comments (2)
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
- Prefab Override popup displays on wrong monitor when Inspector width is resized to minimum
- Scroll View is not moving by inertia after scrolling by click and dragging when Editor window is minimized and Canvas "Render Mode" is set to "World Space"
- "type mismatch error" occurs when the currentDirectionWS output of a Sample Water Surface node is connected to a float3 input
- URP Material Upgrade utility does not enable Alpha Clipping when material had Rendering Mode set to Cutout
- Particle System emission ignores the Sprite Atlas when using a Material that has the "Include in Build" setting unchecked
codestage
May 17, 2016 11:02
You have my voice too! =)
sysameca
Aug 31, 2014 10:15
Yeah this is very annoying and i think this is not how the components should collapse-expand by design.I have on my scene like 20 splines and if i want to work only with few i have to disable the game objects which is very annoying.