Search Issue Tracker
Fixed in 2020.1
Fixed in 2019.3
Votes
0
Found in
2020.1.0
2019.3
2020.1
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
- Shader error db grows on each build
- Android ARCore build fails with 2019.4 due to outdated Gradle
- [tvOS] Visual artifacts are present when Ambient Occlusion is enabled and Dynamic Resolution is reduced
- Texture Importer Inspector throws errors when a built-in texture inspector is overwritten in C#
- Invalid AABB error is thrown when moving a Particle with Velocity over Lifetime and Limit Velocity over Lifetime modules
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