Search Issue Tracker
Fixed
Fixed in 2022.3.23f1, 2023.2.15f1
Votes
0
Found in
2022.3.10f1
2023.2.0b10
Issue ID
UUM-49307
Regression
Yes
PropertyDrawer for child class is ignored when there's a PropertyDrawer for a generic parent class
How to reproduce:
1. Open the attached “PropertiesNames.zip” project
2. In the Project window, select “Bug Demonstrator.asset” file
3. In the Inspector window, observe the PropertyDrawers
Expected result: PropertyDrawers names are: “Base Class Drawer” and “Child Class Drawer”
Actual result: PropertyDrawers names are: “Base Class Drawer” and “Base Class Drawer”
Reproducible with: 2022.3.0f1, 2022.3.10f1, 2023.1.14f1, 2023.2.0b10, 2023.3.0a6
Not reproducible with: 2021.3.30f1, 2022.2.21f
Reproduced on: macOS 13.5.2 (Intel)
Not reproducible on: No other environment tested
Note: this bug only happens if BaseClass is generic. Also, some details seem to influence which of the drawers is used for ChildClass: the alphabetic order of the drawer classes, whether the name of the drawer files matches the drawer classes, and even sometimes the order in which they appear when both drawers are in the same file (user’s info)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Add comment