Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3
2020.1
2020.1.0
Issue ID
1201979
Regression
No
ManagedReference array elements get drawn with wrong PropertyDrawers after array reordering
Reproduction steps:
1. Open attached project "ManagedReferencePropertyDrawer"
2. Create an empty GameObject and add a component of type 'PrefabInterface'
3. Click the button "Add Float" and then "Add Object Field"
4. Observe in the reorderable list that ExposedFloatProperty is drawn with ExposedFloatPropertyDrawer and ExposedObjectProperty is drawn with ExposedObjectPropertyDrawer as expected.
5. Use the handle of the second item to drag it up to become the first item.
Expected result: Both elements are drawn with the correct type of PropertyDrawer.
Actual result: Both elements are drawn with the wrong type of PropertyDrawer.
Reproducible with: 2019.3.0f6, 2020.1.0a20
Could not test with: 2017.4.36f1, 2018.4.17f1, 2019.2.21f1 (SerializeReference attribute not available)
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
- Crash when attempting to create a custom FMOD DSP unit
- [Linux] Floating windows do not keep their size after restarting the Editor
- .framework plugin is mistakenly treated as a directory when building for Universal Windows Platform
- Artifacts appear on GameObjects when using the WebGL Player on Silicon macOS
- Only the icon of the disabled child GameObject is faded when a parent GameObject is a Prefab
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a21, 2019.3.1f1
Resolution Note (fix version 2019.3):
Fixed in 2019.3.1f1