Search Issue Tracker
Fixed in 2020.1.X
Votes
1
Found in
2019.3.0a2
2019.3.0b2
2020.1.0a1
Issue ID
1184232
Regression
No
Enum fields are shown as int fields in the Inspector window when tagging them with SerializeReference attribute
How to reproduce:
1. Open the "SampleScene" in the attached "EnumsAsInts" project
2. Open the Inspector window of the "GameObject"
3. Compare the "Serialize Reference" and "Non Serialize Reference" enum values
Expected results: Both values can be set using a dropdown menu
Actual results: "Serialize Reference Enum" value is set using a text field
Reproducible with: 2019.3.0a2, 2019.3.0b5, 2020.1.0a6
Additional note: Project on versions 2019.3.0a1 and earlier could not be tested due to compilation errors related to SerializeReference
Comments (4)
-
Hotcakes
Sep 04, 2020 23:05
I can still reproduce this (albeit in a slightly modified context by adding the enum itself as another field in the same class) in 2020.1
-
menderbug
Nov 19, 2019 12:21
Looks like this actually did get fixed in 2019.3.0.11b.
-
jynerso
Nov 15, 2019 05:33
why "Won't Fix"??
-
menderbug
Nov 12, 2019 12:50
FWIW, this is not just a visual bug. Custom property drawers which use "property.enumValueIndex" will break inside SerializeReference fields. "property.intValue" can be used as a workaround that works both inside and outside of SerializeReference fields.
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (fix version 2020.1):
Fixed in 2019.3.0b11 and 2020.1.0a13