Search Issue Tracker
Duplicate
Votes
0
Found in
5.2.0b1
Issue ID
709329
Regression
No
[ PropertyDrawer ] Custom foldout on one element of an array affects every element
Reproduction steps:
1. Open attached project
2. Open scene "Test"
3. Select GameObject "Demo"
4. In the Inspector find "Test Array"
5. Try folding and unfolding one of its elements (click a little arrow next to its name)
6. Note, when you do that other elements of "Test Array" also fold and unfold
7. See linked video
Comments (2)
-
Bubsavvy
Oct 06, 2019 23:22
Yeah clearly they don't care. You shouldn't even try... Switch to unreal and you won't have BS issues like this. I feel your pain dude. The only way around it is creating a dictionary<uniquefieldID, bool> and accessing the foldout boolean from there. Sorry for your luck.
-
Icebone1000
Jul 27, 2017 02:53
Why the hell was this closed????
You cant fold ANY property with custom property drawer, unless theres only ONE foldable element. Every folding erlement affects ALL other EditorGUI.Foldout.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #709347