Search Issue Tracker
Fixed in 2019.2.X
Votes
0
Found in
2019.1.0a11
2019.2.0a1
Issue ID
1131012
Regression
Yes
Selection of the array elements in the Inspector is offset when beginning of the array was hidden using the slider
How to reproduce:
1. Open attached project "Case_1131012_repro.zip"
2. Select "ArrayObject" GameObject in the hierarchy
3. In the Inspector, scroll down, so some of the array elements, in the beginning, are not visible
4. Click on the any of the fields of the elements
Expected result: Field, which is behind the mouse cursor is selected
Actual result: Selected field is not the one which is behind the mouse cursor
Reproducible with - 2019.1.0a11, 2019.1.0b5, 2019.2.0a6
Not reproducible with - 2017.4.21f1, 2018.3.7f1, 2019.1.0a10
Notes: Offset is determined by how many elements at the beginning of the array are hidden. If X elements are hidden, selection will be offset by X.
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 (fix version 2019.2):
Fixed in 2019.2.0a9