Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
10.2
Issue ID
1297991
Regression
No
ImGUI vector3 / vector2 alignment for short wided inspector break readability
Step to reproduce:
1 - Display an Inspector that show a Vector2 or a Vector3 using EditorGUILayout.PropertyField (example Collider)
2 - Shorten the wide of the Inspector to the minimal
Expected: All should remain on the same line as it is done in Transform
What happened: It is displayed on two lines for some component.
Additional notes:
- Transform also use a EditorGUILayout.PropertyField(SerializedProperty, GUIContent). I dunno exactly why it remains on one line. I suspect it is linked to the length of the labels.
- Also happens with EditorGUI.MultiFloatField(Rect, GUIContent, GUIContent[], float[])
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
Resolution Note:
This issue is more design oriented that is subjective to users. Having all the fields in one line with a narrow inspector might not be practical/usable at times.